Comment 1 for bug 1426513
Revision history for this message
| Prabhjot Singh Sethi (prabhjot) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
it seems like ovs schema don't have mac as a key in route tables, due to which we end up having two ovs_idl rows in ovsdb-server.
When TOR agent receives this two updates with the virtual network config already avaiable it ends up crashing un able to handle two rows with same mac.
Work Around :- disassociate tor agent from physical router and after connection to TOR associate tor agent again with TOR to recover from this situation.