RabbitMQ unreachable during restart by handler

Bug #1904702 reported by Victor Chembaev
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
High
Victor Chembaev
Train
Fix Released
High
Radosław Piliszek
Ussuri
Fix Released
High
Radosław Piliszek
Victoria
Fix Released
High
Radosław Piliszek
Wallaby
Fix Released
High
Victor Chembaev

Bug Description

Kolla-Ansible versions affected: train+

After applying cluster_partition_handling = pause_minority partition handling policy in train+ k-a release RabbitMQ becomes unreachable for all openstack services during "Restart rabbitmq container (rest of nodes)" task playing. It happens due pause_minority policy freezes the cluster during out of quorum.
Whats happening:
1. Restart rabbitmq container (first node) -> the first node of RMQ cluster has restarted
2. Waiting for rabbitmq to start on first node -> the first node of RMQ cluster is up and running and listen on port
3. Restart rabbitmq container (rest of nodes) -> rest of nodes restarts simultaneously and cluster freezes for all connections until the quorum has return

Tags: rabbitmq
Changed in kolla-ansible:
assignee: nobody → Victor Chembaev (chembervint)
status: New → In Progress
Revision history for this message
Mark Goddard (mgoddard) wrote :
Changed in kolla-ansible:
status: In Progress → Fix Committed
Changed in kolla-ansible:
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 10.2.0

This issue was fixed in the openstack/kolla-ansible 10.2.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 11.0.0.0rc2

This issue was fixed in the openstack/kolla-ansible 11.0.0.0rc2 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 9.3.0

This issue was fixed in the openstack/kolla-ansible 9.3.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 12.0.0.0rc1

This issue was fixed in the openstack/kolla-ansible 12.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.