Rabbitmq doesn't start during cluster re-installation

Bug #1618037 reported by Sergey Novikov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Fuel Sustaining

Bug Description

Detailed bug description:

 Test https://github.com/openstack/fuel-qa/blob/master/fuelweb_test/tests/test_node_reinstallation.py#L355-L386 fails with https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.error_node_reinstallation/42/testReport/(root)/reinstall_failed_primary_controller_deployment/reinstall_failed_primary_controller_deployment/

 In two words, the cluster re-installation after the first failed deployment on primary controller fails on task "primary-rabbitmq". Rabbitmq doesn't start due to the following error:

<30>Aug 29 06:24:38 node-1 lrmd: INFO: p_rabbitmq-server[27889]: get_status(): failed with code 69. Command output: Error: unable to connect to node 'rabbit@messaging-node-1': nodedown

Steps to reproduce:
  1. Create a cluster
  2. Add 3 nodes with controller and mongo roles
  3. Add a node with compute and cinder roles
  4. Provision nodes
  5. Start deployment; fail deployment on primary controller
  6. Reinstall the cluster
  7. Run network verification
  8. Run OSTF

Fuel version http://paste.openstack.org/show/564578/

Tags: swarm-fail
Revision history for this message
Sergey Novikov (snovikov) wrote :
tags: added: swarm-fail
Changed in fuel:
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
importance: Undecided → High
status: New → Confirmed
Changed in fuel:
assignee: Fuel Sustaining (fuel-sustaining-team) → Kyrylo Galanov (kgalanov)
Revision history for this message
Kyrylo Galanov (kgalanov) wrote :

It looks like an environment issue. Please reopen the bug if the issue comes back again.

Changed in fuel:
status: Confirmed → Incomplete
Changed in fuel:
assignee: Kyrylo Galanov (kgalanov) → Fuel Sustaining (fuel-sustaining-team)
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 9.1 → 9.2
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

Marking as Invalid, because of no update for more than a month.

Changed in fuel:
status: Incomplete → Invalid
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.