[SWARM][9.2] add_updated_controller_to_environment fail due rabbitmq_management connection problem

Bug #1674637 reported by Vladimir Jigulin
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
High
Fuel Sustaining

Bug Description

Scenario:
1. Revert snapshot 'base_deploy_3_ctrl_1_cmp'
2. Set local snapshot repo as default for environment
3. Add 1 node with controller role
4. Run network verification
5. Deploy changes

Expected result: deployment is successful.
Actual result: deployment failed. Not all deployments tasks completed.

Errors (#2017-03-16_13-57-39):
curl: (7) Failed to connect to localhost port 15672: Connection refused
...
2017-03-16 13:44:30 +0000 /Stage[main]/Rabbitmq::Install::Rabbitmqadmin/Staging::File[rabbitmqadmin]/Exec[/var/lib/rabbitmq/rabbitmqadmin]/returns (err): change from notrun to 0 failed: curl -k --noproxy localhost --retry 30 --retry-delay 6 -f -L -o /var/lib/rabbitmq/rabbitmqadmin http://nova:EwsoNbMSPeLpnVg1kOTv3sSj@localhost:15672/cli/rabbitmqadmin returned 7 instead of one of [0]

Errors (#2017-03-21_00-10-58):
2017-03-20 23:40:00 +0000 /Stage[main]/Rabbitmq::Management/Rabbitmq_user[guest] (err): Could not evaluate: Command is still failing after 180 seconds expired!
/etc/puppet/modules/rabbitmq/lib/puppet/provider/rabbitmqctl.rb:30:in `run_with_retries'
/etc/puppet/modules/rabbitmq/lib/puppet/provider/rabbitmq_user/rabbitmqctl.rb:61:in `exists?'
...
2017-03-20 23:40:00 +0000 /Stage[main]/Rabbitmq::Management/Rabbitmq_user[guest] (err): Could not evaluate: Command is still failing after 180 seconds expired!
/etc/puppet/modules/rabbitmq/lib/puppet/provider/rabbitmqctl.rb:30:in `run_with_retries'
/etc/puppet/modules/rabbitmq/lib/puppet/provider/rabbitmq_user/rabbitmqctl.rb:61:in `exists?'
/usr/lib/ruby/vendor_ruby/puppet/property/ensure.rb:81:in `retrieve'
/usr/lib/ruby/vendor_ruby/puppet/type.rb:1048:in `retrieve'
/usr/lib/ruby/vendor_ruby/puppet/type.rb:1076:in `retrieve_resource'
/usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:236:in `from_resource'
...

Revision history for this message
Vladimir Jigulin (vjigulin) wrote :
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :
Changed in fuel:
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
milestone: none → 9.x-updates
importance: Undecided → High
status: New → Confirmed
assignee: Fuel Sustaining (fuel-sustaining-team) → Vladimir Jigulin (vjigulin)
Revision history for this message
Vladimir Jigulin (vjigulin) wrote :

Verified on 9.x swarms

Changed in fuel:
status: Confirmed → Fix Released
Revision history for this message
Vladimir Jigulin (vjigulin) wrote :

Seems like test do not fail with this issue anymore

Changed in fuel:
status: Fix Released → Confirmed
Revision history for this message
Vladimir Jigulin (vjigulin) wrote :

Failed again on "9.2 MU-1 iso #04/03/17 13:54" with same issue

Changed in fuel:
assignee: Vladimir Jigulin (vjigulin) → nobody
Changed in fuel:
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
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.