bare metal node partitioning does not handle errors well
Bug #1088655 reported by
Robert Collins
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Vish Ishaya |
Bug Description
When bare metal partitioning fails, ops needs to look in the log to determine the cause - but user requests (such as too-large swap sizes) can cause failures, and so users should get a decent error status set on their instance.
Changed in nova: | |
assignee: | Devananda van der Veen (devananda) → Vish Ishaya (vishvananda) |
Changed in nova: | |
milestone: | none → grizzly-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-3 → 2013.1 |
To post a comment you must log in.
I suspect this happens because of the division between nova-compute and nova-baremetal- deploy- helper. n-cpu calls driver.spawn() and marks the instances as ACTIVE once the machine powers on, while a separate process (nova-baremetal -deploy- helper) does the partitioning and image deployment. Merging these processes would probably resolve this bug.