[2.2] Allow pod syncing to fail for pre-existing or manual composed machines bad physical storage.
Bug #1685891 reported by
Blake Rouse
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Blake Rouse | ||
MAAS RSD |
Fix Released
|
High
|
Blake Rouse |
Bug Description
In some cases Pod drivers will not return all the required information for a physical block device. Instead of failing when the syncing machine is a pre-existing or manually composed it should allow this to fail, since the machine will be commissioned anyway. For dynamic composition it is not possible for it not to provide the required information as commissioning will not be performed.
Related branches
lp:~blake-rouse/maas/sync-bad-physical-blockdevice
- Newell Jensen (community): Approve
-
Diff: 203 lines (+117/-12)2 files modifiedsrc/maasserver/models/bmc.py (+29/-6)
src/maasserver/models/tests/test_bmc.py (+88/-6)
Changed in maasrsd: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Blake Rouse (blake-rouse) |
milestone: | none → beta |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maasrsd: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Changed in maasrsd: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.