Clarify Wait-for-vif-plug event handling
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nova-dpm |
New
|
Medium
|
Andreas Scheuring | ||
Bug Description
Usually the flow during instance boot is like this
* Nova starts listening for vif-plug-events
* Nova creates all the NICS
* Neutron detects that NICs and does some operations on it
* Neutron sneds a vif-plugged event for the NIC to nova
Only if such a event for all NICs was received, nova starts the instance. If such an event is missing, nova will fail with the famous "vif plugging timeout" error.
At the moment this waiting is not implemented. In fact it is not required right now as neutron does not do any modifications to the nic or other networking entities. But this might change in the future.
It might also change once bug [2] is fixed - cause then other things, like the adapter state might be considered before a instance is reported as up.
So the task is to figure out, if with having [2] in mind listening for those events might make sense. If so implement it, if not remove the todo from the code.
[1] https:/
[2] https:/
| Changed in nova-dpm: | |
| assignee: | nobody → Andreas Scheuring (andreas-scheuring) |
| Changed in nova-dpm: | |
| importance: | Undecided → Medium |
| Changed in nova-dpm: | |
| milestone: | none → pike-3 |
