Fix proposed to branch: master Review: https://review.openstack.org/378278
** Changed in: nova Status: Opinion => In Progress ** Changed in: nova Assignee: (unassigned) => Adam Kijak (adam-kijak) -- 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/1627044 Title: Last chance call to neutron if VIF plugin notification is lost Status in OpenStack Compute (nova): In Progress Bug description: While spawning a new VM, Nova waits for event from Neutron that its port is configured. In some cases Neutron event is lost (e.g. RabbitMQ issue) and if vif_plugging_is_fatal=True (it is by default) the instance is set to ERROR state. It happens even if in fact port is ACTIVE on Neutron side and all should work fine. This workflow could be improved by calling Neutron before failing. Nova could check real state of each port in Neutron just before setting the instance in ERROR (if at least one port is not ACTIVE). To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1627044/+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