OpenStack Compute (nova)

Instance remains in scheduling state if RabbitMQ is down during instance creation

Bug #961237 reported by Unmesh Gurjar on 2012-03-21

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=scheduling, power_state=0.

The instance state must be updated to "error" since launching the instance failed.

Tags:

dhanalaxmi (baby-adabala) on 2012-03-28

Changed in nova:
assignee:	nobody → dhanalaxmi (baby-adabala)

Revision history for this message

dhanalaxmi (baby-adabala) wrote on 2012-04-02:

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.

dhanalaxmi (baby-adabala) on 2012-04-17

Changed in nova:
assignee:	dhanalaxmi (baby-adabala) → nobody

Revision history for this message

Mandar Vaze (mandarvaze) wrote on 2012-06-06:

linked to blueprint https://blueprints.launchpad.net/nova/+spec/compute-instance-cleanup-service

Sean Dague (sdague) on 2012-06-07

Changed in nova:
status:	New → Confirmed

Thierry Carrez (ttx) on 2012-06-07

Changed in nova:
importance:	Undecided → Low

Revision history for this message

Rohit Karajgi (rohitk) wrote on 2012-11-06:

This bug was observed in Essex. After the state management changes in Folsom, periodic tasks in Compute
manage this scenario by setting the instance state to Error.

Moreover, after RabbitMQ comes back up, the message casts onto the Scheduler and Compute, the instances gets
spawned and changes state to Active, hence this does not occur anymore.

Marking invalid.