OpenStack Compute (nova)

  1. Bug #961237
  2. Comment #3

Comment 3 for bug 961237

Revision history for this message
Rohit Karajgi (rohitk) wrote :

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.