https://bugzilla.redhat.com/show_bug.cgi?id=1324922
Steven Dake <steven.dake(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |steven.dake(a)gmail.com
--- Comment #3 from Steven Dake <steven.dake(a)gmail.com> ---
I think your speculation is incorrect that the depth logging change, whatever
that was, introduced this regression. The problem was introduced in -16
(adding IPV6 support). This fundamentally changes how epmd operates. epmd
either binds to ipv4 or ipv6, depending on config, but not both.
One workaround mentioned here:
https://github.com/openstack/kolla/blob/master/ansible/roles/rabbitmq/tem...
in comment #6 works on -16, but triggers epmd to bind to 0.0.0.0 (all
interfaces) which could interfere with neutron, then tenant network, etc.
If your going to enable ipv6, might as well fix epmd binding so its handled
properly. btw otp-23 patch is a disaster.
I have yet to try 17 with removal of EPMD binding which would be a good short
term workaround but not a good long term workaround. Long term this will cause
heisenbugs in neutron and other parts of the system that you just haven't
discovered yet ;)
--
You are receiving this mail because:
You are on the CC list for the bug.