Ok, I found the root cause - there is a bug in rabbitmq ocf script with temporary iptables REJECT rule logic and here is the patch for it (already applied in-place at your test envs' controller nodes, Tyler): //review.openstack.org/124121
The fix works for new rabbitmq sessions, but I still have to figure out how to deal with conntrack - removing this REJECT rule does not restore connectivity for running Openstack services.
I mean, restarting the Openstack services would solve the issue completely, but I have to finish the fix as appropriate. Thank you for your cooperation, Tyler.
Ok, I found the root cause - there is a bug in rabbitmq ocf script with temporary iptables REJECT rule logic and here is the patch for it (already applied in-place at your test envs' controller nodes, Tyler): //review. openstack. org/124121
The fix works for new rabbitmq sessions, but I still have to figure out how to deal with conntrack - removing this REJECT rule does not restore connectivity for running Openstack services.
I mean, restarting the Openstack services would solve the issue completely, but I have to finish the fix as appropriate. Thank you for your cooperation, Tyler.