Bug 1592407 - [UPGRADES] RMQ Fails to join cluster after minor update and node's reboot
Summary: [UPGRADES] RMQ Fails to join cluster after minor update and node's reboot
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rabbitmq-server
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: John Eckersberg
QA Contact: pkomarov
URL:
Whiteboard:
Depends On: 1522896
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-18 13:31 UTC by Yurii Prokulevych
Modified: 2019-10-25 11:11 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1522896
Environment:
Last Closed: 2019-10-25 11:11:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 8 pkomarov 2019-05-06 11:33:16 UTC 
Hi , Yuri , 

We don't have automation for all this scenario , what you can do is : 
- get to the point where you have a 12->13 upgrade finished, 
- then you can use our rolling reboot of the overcloud job:
https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DFG/view/pidone/view/rolling_oc_reboot/job/DFG-pidone-rolling_oc_reboot-14_director-rhel-virthost-3cont_2comp_3ceph-ipv4-vxlan-workload_before_after/build?delay=0sec

Since you already have the first part deployed ,in the job : 
- please mark only the stages you need :"Checkout Component", "Install InfraRed" and  "Overcloud Reboot"
-  provide the workspace url at :WORKSPACE_URL
- specify the baremetal fqdn at : IR_PROVISION_HOST

the job will run the overcloud reboot and will halt if any resources (rabbitmq or other) are in state error.
Comment 10 Luca Miccini 2019-10-25 11:11:59 UTC 
This should be fixed in the new resource-agents rpm.
Please reopen if you still experience this issue.
Note You need to log in before you can comment on or make changes to this bug.