[2.0] Disk erasing with Xenial results it abnormal poweroff
Bug #1527634 reported by
Blake Rouse
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Blake Rouse | ||
Bug Description
For an unknown reason when Xenial is set to the commissioning release and your release a node with disk erasing enabled. Xenial will boot but will just poweroff. The disk erasing script itself is never actually ran, its something to do with the cloud-init configuration for disk erasing. Weird thing is that should be identical to commissioning except for the user data. Commissioning with Xenial works as expected.
Related branches
lp:~blake-rouse/maas/fix-1527634
- Andres Rodriguez (community): Approve
-
Diff: 53 lines (+4/-12)2 files modifiedsrc/metadataserver/api.py (+2/-9)
src/metadataserver/tests/test_api_status.py (+2/-3)
| summary: |
- [1.10] Disk erasing with Xenial results it abnormal poweroff + [xenial, 1.10] Disk erasing with Xenial results it abnormal poweroff |
| Changed in maas: | |
| status: | Confirmed → Triaged |
| Changed in maas: | |
| importance: | High → Critical |
| Changed in maas: | |
| milestone: | 1.10.0 → 2.0.0 |
| summary: |
- [xenial, 1.10] Disk erasing with Xenial results it abnormal poweroff + [2.0] Disk erasing with Xenial results it abnormal poweroff |
| Changed in maas: | |
| assignee: | nobody → Blake Rouse (blake-rouse) |
| 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.
