yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1631872] Re: Not all neutron ports are ACTIVE after the vm spawns (hyper-v)

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: OpenStack Infra <1631872@xxxxxxxxxxxxxxxxxx>
Date: Wed, 23 Nov 2016 04:00:19 -0000
Reply-to: Bug 1631872 <1631872@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

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 <cbelu@xxxxxxxxxxxxxxxxxxxxxx>
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


** Changed in: nova
       Status: In Progress => 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/1631872

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

Status in OpenStack Compute (nova):
  Fix Released
Status in tempest:
  In Progress

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