[2.3, wishlist] Enlistment environment should check if the machine is known to MAAS, and act upon it.
Bug #1747928 reported by
Jason Hobbs
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Andres Rodriguez |
Bug Description
In bug 1743249, servers in Deploying state would boot into the ephemeral enlisting environment and then power off, leaving the server in Deploying state to eventually reach Failed Deployment.
MAAS should be able to recognize this situation and have the server do something other than power off. It should be simple to have the server reboot.
The enlistment scripts can ask MAAS if MAAS knows about the server already, and if it's in deploying state - or some other state like commissioning where it should be booting and running stuff, and if so, reboot.
Related branches
~andreserl/maas:enlist_reboot
Merged
into
maas:master
- Blake Rouse (community): Approve
- MAAS Lander: Needs Fixing
-
Diff: 156 lines (+73/-4)4 files modifiedcontrib/preseeds_v2/enlist_userdata (+7/-0)
src/maasserver/api/nodes.py (+17/-0)
src/maasserver/api/tests/test_nodes.py (+38/-0)
src/metadataserver/user_data/templates/snippets/maas_enlist.sh (+11/-4)
Changed in maas: | |
status: | New → Opinion |
milestone: | none → next |
tags: | removed: cdo-qa-blocker |
summary: |
[2.3, wishlist] Enlistment environment should check if the machine is - known to MAAS. + known to MAAS, and act upon it. |
Changed in maas: | |
milestone: | 2.4.x → 2.4.0alpha2 |
assignee: | nobody → Andres Rodriguez (andreserl) |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Why was this marked "Opinion"?