The addition node to cluster fails on rabbitmq/rabbitmq.pp

Bug #1646513 reported by Sergey Novikov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Fuel QA Team

Bug Description

Detailed bug description:
 The issue was found by https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.add_updated_node_to_environment/56/testReport/(root)/add_updated_controller_to_environment/

Steps to reproduce:
            1. Create environment
            2. Add 3 nodes with controller role and 1 node with compute role
            3. Create local mirror for mos
            4. Set local mirror mos as default for environment
            5. Download latest snapshot
            6. Deploy the environment
            7. Set local snapshot repo as default for environment
            8. Add 1 node with controller role
            9. Run network verification
            10. Deploy changes

The deployment fails on http://paste.openstack.org/show/591127/

Description of the environment:
snapshot #578

Revision history for this message
Sergey Novikov (snovikov) wrote :

probably, the reason of failure is difference between rabbitmq's versions on added controller node and existing controllres

root@node-5:~# dpkg -l | grep rabbit
ii rabbitmq-server 3.6.6-1~u14.04+mos2 all Multi-protocol messaging broker

root@node-1:~# dpkg -l | grep rabbit
ii fuel-rabbit-fence 9.0.0-1~u14.04+mos8607 all Fuel RabbitMQ fencing utilitites
ii rabbitmq-server 3.6.5-1~u14.04+mos1 all AMQP server written in Erlang

Changed in fuel:
assignee: nobody → Fuel QA Team (fuel-qa)
Revision history for this message
Sergey Novikov (snovikov) wrote :

we need to make a conclusion: rewrite or delete the corresponding test.

Changed in fuel:
importance: Undecided → Medium
status: New → Confirmed
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.