timing issues in trunk port feature
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-vpp |
Fix Released
|
Undecided
|
Onong Tayeng |
Bug Description
Timing issue #1
The reconsider_
Timing issue #2
A vhostuser interface's admin state is set to UP only when a VM instance has connected to the other end of the interface. So, it is possible that the parent port's vhostuser interface's state is not yet set to UP when ifup() is invoked on the child subport's vhostuser subinterface causing the ifup() to fail. As a result no data can flow on the child subport unless the interface is set UP manually in VPP.
Lastly, another side-effect of these timing issues is that trunk port artifacts in VPP are not cleaned up upon unbind of the parent port.
Changed in networking-vpp: | |
assignee: | nobody → Onong Tayeng (onong) |
This issue is not so much of a problem during the normal running of ML2 agent but it is definitely a problem in the restart/resync situation.