Comment 1 for bug 1727824
Revision history for this message
| James Page (james-page) wrote Re: wrong vip setup for interface | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
I think this is caused by the containers not coming up with consistent network interface naming; the first hacluster unit appears to be trying to configure resources the other way around to the other two units
eth0 eth1
-0 192.xxx 10.245.xxx
-1 10.245.xxx 192.xxx
-2 can't actually tell
resources in the pacemaker cluster for VIP's must have consistent network device naming, so I'm not entirely sure how much we can do about this in the charm. Does juju make any guarantees with regards to network interface ordering when binding network spaces?