lp:~julian-edwards/maas/cluster-name-override-bug-1380805

Created by Julian Edwards and last modified
Get this branch:
bzr branch lp:~julian-edwards/maas/cluster-name-override-bug-1380805
Only Julian Edwards can upload to this branch. If you are Julian Edwards please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Julian Edwards
Project:
MAAS
Status:
Development

Recent revisions

3248. By Julian Edwards

add back defaulting behaviour if the name doesn't exist yet

3247. By Julian Edwards

Don't default cluster_name as it can override the existing name

3246. By Julian Edwards

Failing test

3245. By Julian Edwards

[r=rvb][bug=1376023][author=julian-edwards] Don't crash when trying to do bulk release on nodes without an owner. This is caused by corrupt data somehow, but nonetheless MAAS should not crash.

3244. By Raphaël Badin

[r=allenap,gmb][bug=1375360][author=rvb] Run dhclient on all the unconfigured interfaces during commissioning to create links between the NICs attached to unconfigured interfaces and the networks MAAS knows about.

3243. By Graham Binns

[r=rvb,allenap][bug=1365591][author=gmb] The "Start node" button in the UI now:
 - Also acquires the node for the user if it hasn't already been acquired.
 - Displays "Acquire and start node" if the node isn't allocated to the user, and "Start node" if it is.

Per comments on bug 1365591, I considered adding "(with default options)" to the button label, but until bug 1379187 is fixed, this is kind of meaningless and confusing.

3242. By Graham Binns

[r=rvb,julian-edwards][bug=1380470][author=gmb] Add the username of the user who acquired a node to the the node's event log when the node transitions to ALLOCATED.

Previously, we didn't record the user's name anywhere; this changes makes that particular event log more useful.

3241. By Graham Binns

[r=kiko,allenap][bug=1379401][author=gmb] If we encounter an IntegrityError in EventManager.register_event_type_and_event(), catch the error and try to fetch the EventType again.

An IntegrityError will be raised when another thread has created the EventType before we called create(), but because it happened in a separate thread (and thus a separate transaction) Django doesn't know about it and doesn't create a ValidationError like you'd expect. Instead the error comes from the DB.

Our solution is not elegant, but should work for the majority of cases (and if we get a case where the EventType exists in the DB but doesn't get returned by get() then we've got bigger and weirder problems).

Another solution for this would have been to lock the table whilst we inserted the EventType row, but that just seems
 a) Like overkill
 and
 b) Not easy to do in Django-land.

We could shave yaks on this all day, but I suspect that this patch will fix the bug just fine.

3240. By Newell Jensen

[r=kiko,rvb,julian-edwards][bug=1378910][author=newell-jensen] Adding regular expression to the nodes view for a better *looking* installation result link name. This will take the installation result name (file name of installation result sent to MAAS from curtin) and make it more presentable. For example, currently in the node's Installation Output the link is: "curtin_install.log". With this change it would become: "curtin install log" and with the other branch in curtin for this bug it will ultimately become: "install log".

3239. By Jeroen T. Vermeulen

[r=rvb][bug=][author=jtv] Update IPv6 documentation. Remove some documented limitations: IPv6 is no longer restricted to 64-bit netmasks, and IPv6-only and dual-stack nodes deploy just fine without route advertisements on the network.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:~maas-committers/maas/trunk
This branch contains Public information 
Everyone can see this information.

Subscribers