Instance remains in scheduling state if RabbitMQ is down during instance creation
Bug #961237 reported by
Unmesh Gurjar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Low
|
Unassigned |
Bug Description
Scenario: Stop the RabbitMQ server and try launching an instance.
Branch: master
Expected Result: The instance must go into error state.
Actual Result: Instance goes into vm_state=building, task_state=
The instance state must be updated to "error" since launching the instance failed.
Changed in nova: | |
assignee: | nobody → dhanalaxmi (baby-adabala) |
Changed in nova: | |
assignee: | dhanalaxmi (baby-adabala) → nobody |
Changed in nova: | |
status: | New → Confirmed |
Changed in nova: | |
importance: | Undecided → Low |
To post a comment you must log in.
Hi,
If we stop RabbitMQ server and create a new instance, the instance is in "BUILD" state.
After starting the RabbitMQ server, instance state is changed from 'BUILD' to 'ACTIVE'.
This is tested in Essex version.