Comment 17 for bug 1794991
Revision history for this message
| Swaminathan Vasudevan (swaminathan-vasudevan) wrote | #17 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Yes I think the problem is when a first VM on that network is created for a node, the l2pop rules have to be populated properly, given the criteria, that the tunnel interfaces are created properly and the vlan manager has configured the vlan mapping, then if everything is in place, the l2pop rules will be populated properly.
If anyone of these are missing then it may error out and not configure the l2pop rules for the network.
Any new networks that are created, may not have this problem, probably if the tunnel interfaces and the vlan mapping are configured right.
The most important thing that we need to figure out is if there is a race between the tunnel interface create/vlan mapping and the l2pop flow add.