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

Bug #1631872 reported by Claudiu Belu on 2016-10-10
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Claudiu Belu
Claudiu Belu

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].


Changed in tempest:
assignee: nobody → Claudiu Belu (cbelu)
status: New → In Progress
Changed in tempest:
assignee: Claudiu Belu (cbelu) → Adelina Tuvenie (atuvenie)
Matt Riedemann (mriedem) wrote :

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.

summary: - Not all neutron ports are ACTIVE after the vm spawns
+ Not all neutron ports are ACTIVE after the vm spawns (hyper-v)
Changed in nova:
status: New → Triaged
importance: Undecided → Medium
tags: added: hyper-v neutron
Changed in nova:
assignee: nobody → Anusha Unnam (anusha-unnam)

Fix proposed to branch: master

Changed in nova:
assignee: Anusha Unnam (anusha-unnam) → Claudiu Belu (cbelu)
status: Triaged → In Progress
Matt Riedemann (mriedem) wrote :
Changed in nova:
importance: Medium → High

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

Changed in nova:
status: In Progress → Fix Released
Changed in tempest:
assignee: Adelina Tuvenie (atuvenie) → Claudiu Belu (cbelu)

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

Ken'ichi Ohmichi (oomichi) wrote :

As I mentioned on , we don't need to change Tempest side for this.

Changed in tempest:
status: In Progress → Won't Fix
Changed in tempest:
status: Won't Fix → In Progress
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related blueprints