Rabbitmq::Install::Rabbitmqadmin fails during deploy after replacing primary controller

Bug #1589518 reported by ElenaRossokhina
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Oleksiy Molchanov
Mitaka
Invalid
High
Oleksiy Molchanov

Bug Description

Detailed bug description:
Rabbitmq::Install::Rabbitmqadmin fails during deploy after replacing primary controller and adding one more controller.
Steps to reproduce:
1. Create cluster
2. Add 3 controller nodes and 1 compute
3. Deploy the cluster
4. Destroy primary controller
5. Wait controller offline
6. Remove offline controller from cluster (I used GUI, button "Remove" near node status label)
7. Add 1 new controller
8. Deploy changes
Expected results:
Deploy OK
Actual result:
All nodes have Error status;
puppet.log on new controller node contains:
(/Stage[main]/Rabbitmq::Management/Rabbitmq_user[guest]) Could not evaluate: Command is still failing after 180 seconds expired!
(/Stage[main]/Rabbitmq::Install::Rabbitmqadmin/Staging::File[rabbitmqadmin]/Exec[/var/lib/rabbitmq/rabbitmqadmin]/returns) change from notrun to 0 failed: curl -k --noproxy localhost --retry 30 --retry-delay 6 -f -L -o /var/lib/rabbitmq/rabbitmqadmin http://nova:ZVpDslAthkbNtSF8yhroxIrn@localhost:15672/cli/rabbitmqadmin returned 7 instead of one of [0]

fuel-9.0-mos-427-2016-06-01_12-18-59.iso:
cat /etc/fuel_build_id:
 427
cat /etc/fuel_build_number:
 427
cat /etc/fuel_release:
 9.0
cat /etc/fuel_openstack_version:
 mitaka-9.0
rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun':
 fuel-release-9.0.0-1.mos6347.noarch
 fuel-misc-9.0.0-1.mos8415.noarch
 fuel-bootstrap-cli-9.0.0-1.mos284.noarch
 fuel-migrate-9.0.0-1.mos8415.noarch
 rubygem-astute-9.0.0-1.mos747.noarch
 fuel-provisioning-scripts-9.0.0-1.mos8718.noarch
 network-checker-9.0.0-1.mos72.x86_64
 fuel-mirror-9.0.0-1.mos137.noarch
 fuel-openstack-metadata-9.0.0-1.mos8718.noarch
 fuel-notify-9.0.0-1.mos8415.noarch
 nailgun-mcagents-9.0.0-1.mos747.noarch
 python-fuelclient-9.0.0-1.mos319.noarch
 fuelmenu-9.0.0-1.mos270.noarch
 fuel-9.0.0-1.mos6347.noarch
 fuel-utils-9.0.0-1.mos8415.noarch
 fuel-setup-9.0.0-1.mos6347.noarch
 fuel-library9.0-9.0.0-1.mos8415.noarch
 shotgun-9.0.0-1.mos90.noarch
 fuel-agent-9.0.0-1.mos284.noarch
 fuel-ui-9.0.0-1.mos2710.noarch
 fuel-ostf-9.0.0-1.mos934.noarch
 python-packetary-9.0.0-1.mos137.noarch
 fuel-nailgun-9.0.0-1.mos8718.noarch
Diagnostic snapshot is available here https://drive.google.com/open?id=0B2ag_Bf-ShtTMjdUQTBNc0lPR3M

Revision history for this message
ElenaRossokhina (esolomina) wrote :

Also, issue was reproduced on another scenario:

1. Deploy cluster: 1 controller, Neutron Vlan, default storages
2. Run OSTF
3. Add 2 controllers
4. Re-deploy cluster (FAIL)

full snapshot https://drive.google.com/open?id=0B2ag_Bf-ShtTZ3dhTzVSX2VHUVk

tags: added: area-library
Changed in fuel:
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
Maciej Relewicz (rlu)
Changed in fuel:
milestone: none → 9.0
importance: Undecided → High
status: New → Confirmed
Changed in fuel:
assignee: Fuel Sustaining (fuel-sustaining-team) → Oleksiy Molchanov (omolchanov)
Changed in fuel:
importance: High → Medium
importance: Medium → High
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

Not reproduced on latest ISO. Please provide env if it is possible.

Changed in fuel:
status: Confirmed → Incomplete
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 9.0 → 10.0
tags: added: move-to-mu
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

We have checked environment provided by TS. Env is extremely slow, it caused such failures. That's why I was not able to reproduce. Marking this as Invalid.

Changed in fuel:
status: Incomplete → Invalid
tags: added: swarm-fail
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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