Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1592407

Summary: [UPGRADES] RMQ Fails to join cluster after minor update and node's reboot
Product: Red Hat OpenStack Reporter: Yurii Prokulevych <yprokule>
Component: rabbitmq-serverAssignee: John Eckersberg <jeckersb>
Status: CLOSED CURRENTRELEASE QA Contact: pkomarov
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: apevec, augol, chjones, jeckersb, jjoyce, jschluet, lbezdick, lhh, lmiccini, mbultel, mcornea, michele, pkomarov, rbartal, sclewis, slinaber, srevivo, tvignaud, ushkalim
Target Milestone: ---Keywords: ReleaseNotes, Triaged, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1522896 Environment:
Last Closed: 2019-10-25 11:11:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1522896    
Bug Blocks:    

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.