wrong vip setup for interface when network interface naming is not consistent across units.
Bug #1727824 reported by
Jason Hobbs
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Incomplete
|
Low
|
John A Meinel | ||
OpenStack Neutron API Charm |
Triaged
|
Medium
|
Unassigned |
Bug Description
I'm using neutron-api with two VIPs:
value of "vip" config: 10.245.208.97 192.168.33.9
eth0 is on 10.245.208.x and eth1 is on 192.168.33.x:
http://
However, the same vip is getting setup for both interfaces:
http://
Here is the bundle we're using:
https:/
juju logs are available here: https:/
Changed in juju: | |
assignee: | nobody → John A Meinel (jameinel) |
To post a comment you must log in.
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?