Public bug reported:
In case if evacuation or rebuild fails there is a possibility to have more than
one records for a failed evacuation in 'accepted' state.
At the same time, _destroy_evacuated_instances() in
nova.compute.manager.ComputeManager performs db query in assumption that there
is just one single db record for the failed evacuation.
As a result, one row will be updated and all other rows will remain for next
call of _destroy_evacuated_instances().
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1779868
Title:
Evacuate/rebuild fail mail cause inconsistent requests to nova
database
Status in OpenStack Compute (nova):
New
Bug description:
In case if evacuation or rebuild fails there is a possibility to have more
than one records for a failed evacuation in 'accepted' state.
At the same time, _destroy_evacuated_instances() in
nova.compute.manager.ComputeManager performs db query in assumption that there
is just one single db record for the failed evacuation.
As a result, one row will be updated and all other rows will remain for next
call of _destroy_evacuated_instances().
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1779868/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
