Latest Xena Rabbit Binding to 0.0.0.0 and Breaking Haproxy
Bug #1961532 reported by
Boris Lukashev
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla-ansible |
New
|
Undecided
|
Unassigned | ||
Bug Description
During our current in-release upgrade to newer Xena pieces, we saw rabbit failing to start during the upgrade. Logs show that the management port is already bound on the VIP by haproxy and that beam.smp is trying to bind 0.0.0.0 despite the bind address being set in its environment by Kolla. Obviously this trashes the upgrade and all of openstack. we had to manually change the haproxy-bound port to get rabbit back, not sure what we broke by doing that yet.
To post a comment you must log in.
