There are no currently open reviews on this bug, changing the status
back to the previous state and unassigning. If there are active reviews
related to this bug, please include links in comments.
** Changed in: nova
Status: In Progress => Opinion
** Changed in: nova
Assignee: Adam
** No longer affects: neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1627044
Title:
Last chance call to neutron if VIF plugin notification is lost
Status in OpenStack Compute
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1627044
Title:
Last chance call to neutron if VIF plugin notification
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
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
5 matches
Mail list logo
