MAAS

[xenial, 1.10] enlistment failing

Bug #1526532 reported by Ricardo Bánffy
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Blake Rouse
MAAS 1.10.0

Bug Description

Running 1.10.0~alpha1+bzr4556-0ubuntu1~xenial1 and attempting to enlist a node with Xenial instead of Trusty (via a manual patch to /usr/share/distro-info/ubuntu.csv so MAAS thinks Xenial is production-ready). The node fails to enlist.

Tags: python3

Related branches

lp:~blake-rouse/maas/fix-xenial-poweroff
Mike Pontillo (community): Approve
Diff: 403 lines (+70/-153)
10 files modified
contrib/preseeds_v2/enlist_userdata (+7/-31)
etc/maas/templates/commissioning-user-data/user_data.template (+0/-36)
etc/maas/templates/commissioning-user-data/user_data_disk_erasing.template (+0/-36)
etc/maas/templates/commissioning-user-data/user_data_poweroff.template (+2/-39)
src/maasserver/compose_preseed.py (+21/-3)
src/maasserver/tests/test_compose_preseed.py (+22/-0)
src/maasserver/websockets/protocol.py (+4/-2)
src/metadataserver/models/commissioningscript.py (+3/-0)
src/metadataserver/models/tests/ip_addr_results.txt (+11/-5)
src/metadataserver/user_data/tests/test_poweroff.py (+0/-1)
Revision history for this message
Ricardo Bánffy (rbanffy) wrote :

Not sure why they didn't attach the first time.

tags: added: python3
summary: - [xenial, 1.10] enlistment failing to power off the node
+ [xenial, 1.10] enlistment failing
Blake Rouse (blake-rouse)
Changed in maas:
status: Triaged → In Progress
assignee: nobody → Blake Rouse (blake-rouse)
milestone: none → next
MAAS Lander (maas-lander)
Changed in maas:
status: In Progress → Fix Committed
Andres Rodriguez (andreserl)
Changed in maas:
milestone: next → 1.10.0
Revision history for this message
Junien F (axino) wrote :

Hi,

Since xenial is officially released, I believe anyone syncing images from images.maas.io is forced to use xenial for node commissioning, so this fix needs to be backported ASAP to all supported MAAS versions.

It would appear that the Ubuntu version used for commissioning is forced to the last LTS, and can't be changed in any way from the web UI or the CLI.

I had to resort to the following patch to be able to commission nodes again :
$ diff -u /tmp/ubuntu.py /usr/lib/python2.7/dist-packages/provisioningserver/drivers/osystem/ubuntu.py
--- /tmp/ubuntu.py 2016-04-25 09:15:44.016351975 +0000
+++ /usr/lib/python2.7/dist-packages/provisioningserver/drivers/osystem/ubuntu.py 2016-04-25 08:05:44.625399234 +0000
@@ -57,7 +57,8 @@
         only exists on Ubuntu, because that is the only operating
         system that supports commissioning.
         """
- return [self.get_lts_release()]
+ return ["trusty"]

Thanks

Andres Rodriguez (andreserl)
no longer affects: maas (Ubuntu)
Revision history for this message
Junien F (axino) wrote :

My issue has been fixed in LP#1573046.

Thanks !

Andres Rodriguez (andreserl)
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.