As I mentioned on https://review.openstack.org/#/c/383049/ , we don't need to change Tempest side for this.
** Changed in: tempest Status: In Progress => Won't Fix -- 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/1631872 Title: Not all neutron ports are ACTIVE after the vm spawns (hyper-v) Status in OpenStack Compute (nova): Fix Released Status in tempest: Won't Fix Bug description: Currently, the nova Hyper-V driver does not wait for neutron vif plug events (or, in case of other drivers, nova-compute can be configured not to wait for neutron vif plug events), which means that by the time the VM becomes ACTIVE, there's no guarantee that the ports have been bound and became ACTIVE. Because, of this, some tests which require connecting to the VM via a floating ip, will randomly fail [1], as tempest will filter out ports that are not active, raising an exception [2]. [1] http://paste.openstack.org/show/584712/ [2] https://github.com/openstack/tempest/blob/master/tempest/scenario/manager.py#L800 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1631872/+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