negative "rescue" tempest tests fail, cannot pause/rescue while instance is in vm_state building
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Expired
|
Undecided
|
Unassigned |
Bug Description
A tempest run failed several tests with errors like "Cannot 'pause' while instance is in vm_state building". The other things tempest was trying to do is 'rescue' and 'attach_volume', and they all failed with the same error.
Also, the error reported was "Conflict: An object with that identifier already exists" -- but there wasn't a conflict because an object with that identifier exists... it's a conflict with the state.
Here's the tests that failed, in tempest.
.ServerRescueNe
.ServerRescueNe
.ServerRescueNe
n-cpu:
2014-03-10 22:43:00.681 21160 INFO nova.virt.
2014-03-10 22:43:00.684 DEBUG nova.compute.
n-api:
2014-03-10 22:43:01.193 INFO nova.api.
Looks like the request doesn't get from api to cpu, since api thinks it's not ready.
tags: | added: testing |
An example here logs.openstack. org/78/ 82178/1/ check/check- tempest- dsvm-neutron- full/026c1b6/ console. html.gz
http://