RabbitMQ nodes is not equal to number of cluster nodes after add/delete controller nodes

Bug #1705523 reported by Ilya Bumarskov
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
MOS Maintenance

Bug Description

Steps to reproduce:
            1. Create cluster
            2. Add 1 controller node
            3. Deploy the cluster
            4. Add 2 controller nodes
            5. Deploy changes
            6. Add 2 controller 1 compute nodes
            7. Deploy changes
            8. Run OSTF
            9. Delete the primary and the last added controller.
            10. Deploy changes
            11. Run OSTF

Observed behaviour:
Failed OSTF test:
  - RabbitMQ availability (failure) Number of RabbitMQ nodes is not equal to number of cluster nodes.

Were affected several jobs:

Related bug: https://bugs.launchpad.net/mos/+bug/1653722

Changed in mos:
importance: Undecided → High
assignee: nobody → MOS Maintenance (mos-maintenance)
description: updated
Changed in mos:
milestone: none → 8.0-updates
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.