OS API: Servers become stuck in rebuild if flavor does not meet flavor reqs of new image
Bug #919367 reported by
Daryl Walleck
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Medium
|
Dan Prince | ||
Bug Description
I did this by accident. I noticed that I had a server stuck in rebuild, and realized that I had tried to rebuild my 256 MB instance into an image that had had a RAM requirement of 1024MB. It won't change state and can't be deleted, so this seems incorrect.
| Changed in nova: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
Revision history for this message
| Naveed Massjouni (ironcamel) wrote | #1 |
Revision history for this message
| Daryl Walleck (dwalleck) wrote | #2 |
| Changed in nova: | |
| assignee: | nobody → Dan Prince (dan-prince) |
Revision history for this message
| Dan Prince (dan-prince) wrote | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #4 |
| Changed in nova: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova (master) | #5 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → folsom-1 |
| Changed in nova: | |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | folsom-1 → 2012.2 |
To post a comment you must log in.
Can you please provide the relevant nova compute log lines. This is hard to reproduce in my dev environment because I don't have any images with large RAM requirements.