Last chance call to neutron if VIF plugin notification is lost
Bug #1627044 reported by
Adam Kijak
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Opinion
|
Wishlist
|
Unassigned |
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_
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).
description: | updated |
description: | updated |
no longer affects: | neutron |
To post a comment you must log in.
Seems like a decent idea worth pushing a patch to see how this looks, but it could get complicated based on how this code is plumbed. It's really the spawn method in the virt driver that's waiting for the event, not the compute manager, and the virt driver doesn't have a handle to the network API to make the port GET call to neutron to check this. I'm sure something could be worked into the wait code for a final callback method to use if provided and a timeout is reached.