Comment 4 for bug 1154622
Revision history for this message
| Robert van Leeuwen (rovanleeuwen) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Daneyon, did you get this to work?
I'm hitting the same issue it seems.
Adding a second L3-agent will always result in a "Failed scheduling router" message.
I've tried disabling the router-agent first (This will result in a "is not a L3 Agent or has been disabled")