Not all neutron ports are ACTIVE after the vm spawns (hyper-v)

[Claudiu Belu]

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

[Matt Riedemann (mriedem)]

This needs to be fixed in the hyper-v driver in nova also, anything using neutron should have the code that waits for the vif plugged event before making the server as ACTIVE. Clients expect that once the server is ACTIVE they can ssh into it and perform other operations on it.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/399001

[Matt Riedemann (mriedem)]

https://review.openstack.org/#/c/399001/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/399001
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=00fdf284085866c77590255059ae74b672dd5a85
Submitter: Jenkins
Branch: master

commit 00fdf284085866c77590255059ae74b672dd5a85
Author: Claudiu Belu <email address hidden>
Date: Thu Nov 17 13:10:06 2016 +0200

    hyper-v: wait for neutron vif plug events

    During spawn, the Hyper-V driver should wait for the Neutron
    VIF plug events before starting the instance, in order to ensure
    that the VIFs are already bound and the guest will be able to
    send DHCP requests.

    The configuration option "vif_plugging_timeout" will determine
    the maximum amount of time to wait for the Neutron events.

    Setting the configuration option "vif_plugging_is_fatal" to True
    will cause an exception to be raised during spawn, if the Hyper-V
    driver did not receive needed Neutron port bound events.

    Closes-Bug: #1631872

    Change-Id: Ie8b4cc64f580aca1115d88258728ab90241d112b

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/nova 15.0.0.0b2 development milestone.

[Ken'ichi Ohmichi (oomichi)]

As I mentioned on https://review.openstack.org/#/c/383049/ , we don't need to change Tempest side for this.

[Martin Kopec (mkopec)]

Seems like this got accidentally from Won't Fix state to InProgress without explanation why and any further work. Therefore I'm gonna move it back to Won't Fix. If you feel like this should be addressed , please provide the current info (as the bug is ~2 years old -> tempest code base has changed dramatically since then) and feel free to reopen.