** Changed in: tempest Status: Fix Committed => Fix Released -- 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/1486475
Title: Transient mismatch between OS-EXT-STS:vm_state and OS-EXT- STS:power_state Status in OpenStack Compute (nova): Confirmed Status in tempest: Fix Released Bug 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.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 ? To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1486475/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp