© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
According to this:
octavia/2 /etc/haproxy/
backend octavia-
balance leastconn
server octavia-2 10.246.65.140:9866 check
server octavia-0 10.246.65.169:9866 check
server octavia-1 None:9866 check
server octavia-3 10.246.65.110:9866 check
vs
octavia/0 - just right
backend octavia-
balance leastconn
server octavia-0 10.246.65.169:9866 check
server octavia-2 10.246.65.140:9866 check
server octavia-3 10.246.65.110:9866 check
And the original statement:
A server was taken down for maintenance. It's old units were removed from the juju model. Then re-added when the host was back in commission.
It sounds like octavia-1 was removed, and then when the machine was back up, we introduced octavia-3.
Which means the fact that octavia-2 is still thinking about octavia-1 is the problem, as octavia-1 definitely doesn't have an IP address anymore.
Now I don't know why octavia-3 doesn't know about octavia-2
octavia/3 - too few
backend octavia-
balance leastconn
server octavia-3 10.246.65.110:9866 check
server octavia-0 10.246.65.169:9866 check
Potentially the fact that octavia-2 is still thinking about octavia-1 is causing a problem in the charm, causing it to not respond to relation-joined from octavia-3, so octavia-3 is not then seeing octavia-2. If that were happening, I'd definitely expect to see charms in error state and errors in the Juju unit logs.