Public bug reported:
This applies only when the nova/neutron event reporting mechanism is
enabled.
It has been observed that in some cases Nova spawns an instance without
waiting for network-vif-plugged event, even if the vif was unplugged and
then plugged again.
This happens because the status of the VIF in the network info cache is not
updated when such events are received.
Therefore the cache contains an out-of-date value and the VIF might already be
in status ACTIVE when the instance is being spawned. However there is no
guarantee that this would be the actual status of the VIF.
For instance in this case there are only two instances in which nova
starts waiting for 'network-vif-plugged' on f800d4a8-0a01-475f-
bd34-8d975ce6f1ab. However this instance is used in
tempest.api.compute.servers.test_server_actions, and the tests in this
suite should trigger more than 2 events requiring a respawn of an
instance after unplugging vifs.
>From what can be gathered by logs, this issue, if confirmed, should
occur only when actions such as stop, resize, reboot_hard are executed
on a instance.
** Affects: nova
Importance: Undecided
Status: New
--
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/1338672
Title:
Nova might spawn without waiting for network-vif-plugged event
Status in OpenStack Compute (Nova):
New
Bug description:
This applies only when the nova/neutron event reporting mechanism is
enabled.
It has been observed that in some cases Nova spawns an instance
without waiting for network-vif-plugged event, even if the vif was
unplugged and then plugged again.
This happens because the status of the VIF in the network info cache is not
updated when such events are received.
Therefore the cache contains an out-of-date value and the VIF might already
be in status ACTIVE when the instance is being spawned. However there is no
guarantee that this would be the actual status of the VIF.
For instance in this case there are only two instances in which nova
starts waiting for 'network-vif-plugged' on f800d4a8-0a01-475f-
bd34-8d975ce6f1ab. However this instance is used in
tempest.api.compute.servers.test_server_actions, and the tests in this
suite should trigger more than 2 events requiring a respawn of an
instance after unplugging vifs.
From what can be gathered by logs, this issue, if confirmed, should
occur only when actions such as stop, resize, reboot_hard are executed
on a instance.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1338672/+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
