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.
** Also affects: nova
Importance: Undecided
Status: New
** Summary changed:
- 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
** Changed in: nova
Importance: Undecided => Medium
** Tags added: hyper-v neutron
--
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):
Triaged
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
--
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
