MAAS 2.9 RC1 does not enlist with ubuntu 16.04
Bug #1904267 reported by
Bart Vrancken
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Lee Trager | ||
| 2.9 |
Fix Released
|
High
|
Adam Collard | ||
Bug Description
The enlisting never happens using Ubuntu 16.04. This was the solution for people to keep using Wake-On-LAN. No errors are logged, the enlistment-machine just reboots before starting the tasks en never shows up as a machine.
Request:
- either fix this image OR
- make ubuntu 16.04 unselectable for enlistment/
Related branches
~adam-collard/maas:2.9-lp1904267
- Adam Collard (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 114 lines (+54/-15)2 files modifiedsrc/metadataserver/user_data/templates/snippets/maas_run_remote_scripts.py (+32/-15)
src/metadataserver/user_data/templates/snippets/tests/test_maas_run_remote_scripts.py (+22/-0)
~ltrager/maas:lp1904267
- Björn Tillenius: Approve
- MAAS Lander: Approve
-
Diff: 114 lines (+54/-15)2 files modifiedsrc/metadataserver/user_data/templates/snippets/maas_run_remote_scripts.py (+32/-15)
src/metadataserver/user_data/templates/snippets/tests/test_maas_run_remote_scripts.py (+22/-0)
Revision history for this message
| Lee Trager (ltrager) wrote | #1 |
| Changed in maas: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Lee Trager (ltrager) |
| milestone: | none → 2.9.0rc2 |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| milestone: | 2.9.0rc2 → 2.10-next |
| Changed in maas: | |
| milestone: | 3.0.0 → none |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Commissioning works in 16.04 but it does look like enlistment fails. This may be due to the rework I did to enable logging BMC detection.