| 2015-09-01 07:21:17 |
Attila Fazekas |
description |
Hi,
I got this weird Tempest run here: http://logs.openstack.org/35/206935/1/gate/gate-tempest-dsvm-neutron-full/ef5a1a9/console.html#_2015-08-18_18_20_26_980 where the server has "OS-EXT-STS:vm_state": "active" and "OS-EXT-STS:power_state": 3.
Power_state 3 is "PAUSED" according to nova/compute/power_state.py So it seems there"s a kind of mismatch with the vm_state being "active".
The discrepancy last only a fraction of second, but as Tempest is hitting hard on Nova, Tempest got into this intermediary state and my build was marked as "failed".
Could someone confirm that right after the VM transitioned from BUILD/spawning to ACTIVE/None there could be a window of inconsistency ? |
Hi,
I got this weird Tempest run here: http://logs.openstack.org/35/206935/1/gate/gate-tempest-dsvm-neutron-full/ef5a1a9/console.html.gz#_2015-08-18_18_20_26_980 where the server has "OS-EXT-STS:vm_state": "active" and "OS-EXT-STS:power_state": 3.
Power_state 3 is "PAUSED" according to nova/compute/power_state.py So it seems there"s a kind of mismatch with the vm_state being "active".
The discrepancy last only a fraction of second, but as Tempest is hitting hard on Nova, Tempest got into this intermediary state and my build was marked as "failed".
Could someone confirm that right after the VM transitioned from BUILD/spawning to ACTIVE/None there could be a window of inconsistency ? |
|
