Bug 2224527

Summary: After cephadm adoption, HAProxy fails to start when RGW is deployed
Product: Red Hat OpenStack Reporter: Francesco Pantano <fpantano>
Component: documentationAssignee: Jenny-Anne Lynch <jelynch>
Status: RELEASE_PENDING --- QA Contact: RHOS Documentation Team <rhos-docs>
Severity: high Docs Contact:
Priority: high    
Version: 17.1 (Wallaby)CC: alfrgarc, arcsingh, ceph-eng-bugs, cephqe-warriors, gfidente, gmeno, jelynch, johfulto, kgilliga, kthakre, mkatari, msaini, sostapov, tonay
Target Milestone: gaKeywords: Documentation, Triaged
Target Release: 17.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
There is currently a known issue with the upgrade from RHOSP 16.2 to 17.1, when RADOS Gateway (RGW) is deployed as part of director-deployed Red Hat Ceph Storage. The procedure fails when HAProxy does not restart on the next stack update. Workaround: Apply the workaround from Red Hat KCS solution 7025985: link:https://access.redhat.com/solutions/7025985[HAProxy does not restart during RHOSP upgrade when RHCS is director-deployed and RGW is enabled]
Story Points: ---
Clone Of: 2224351 Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 4 Khomesh Thakre 2023-07-26 10:01:57 UTC
Hello Francesco, I am working on creating a WA for CI. 

Is there a way we can apply the workaround proactively to avoid the issue?

Thanks