Bug 1876852
Summary: | [External Mode] ceph-external-cluster-details-exporter.py does not tolerate TLS enabled RGW | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat OpenShift Container Storage | Reporter: | Mauro Oddi <moddi> | |
Component: | rook | Assignee: | arun kumar mohan <amohan> | |
Status: | CLOSED NEXTRELEASE | QA Contact: | Rachael <rgeorge> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 4.5 | CC: | amohan, assingh, ebenahar, jelopez, madam, muagarwa, nberry, ocs-bugs, ratamir, shan | |
Target Milestone: | --- | Keywords: | AutomationBackLog | |
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1878853 (view as bug list) | Environment: | ||
Last Closed: | 2020-12-16 08:45:24 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: | ||||
Bug Blocks: | 1878853 |
Description
Mauro Oddi
2020-09-08 11:01:45 UTC
Arun PTAL. Will be in the next z-stream Ack. Looking into it.. @Ashish, I remember you tried RGW with HA-Proxy enabled. Did you also face the same issue ? Raised PR: https://github.com/rook/rook/pull/6227 @Sebastian, please take a look. @seb, in order to move to another release, you do not only need to add the new release flag, but also remove the old one. :-) Hey Neha, No, I did not try the RGW behind HAProxy, we just discussed that if the Customer wants to use multiple RGW for load balancing, he should use HAProxy. Regards, Ashish Singh Moving it back to POST because the fix was reverted. Also, please do not merge it in Downstream 4.5 till we have all the acks and downstream is open for check-ins. Hi Mudit, Is there a particular reason for backporting the fix in 4.5.z. If it is urgent and must-fix for 4.5.z, are we planning it for 4.5.2, since 4.5.1 is a minimal release ? We will backport it in 4.5.2 only, there is no plan to put this in 4.5.1 The confusion here is because Seb merged it into 4.5 branch by mistake but later reverted the same, so the fix is not there in 4.5.z and it won't be there till we start accepting the changes for 4.5.2 https://github.com/openshift/rook/pull/122/ is actually a revert PR. For now, not qa acking. Will do once we will start planning the 2nd 4.5 z-stream This BZ doesn't have any acks and as of now there are no plans for next 4.5.z, is there any reason to merge https://github.com/openshift/rook/pull/148 to 4.5? tbh I have no idea, Arun did the patch and requested review only, so I assumed everything was in place BZ wise... Can we get a QE ack for it, if we do feel it's going to be in a 4.5.z? Or close... Yaniv, We are not planning 4.5.z so this needs to be retargeted to 4.6.z. I think the fix is already there in 4.6, Arun can you please confirm the same? > I think the fix is already there in 4.6, Arun can you please confirm the same? Yes it is already backported to `openshift/rook` release-4.6 branch... https://github.com/openshift/rook/commit/1b17580f39e76faf4fd8c5ab89cd38ab7cb917fd File#line: https://github.com/openshift/rook/blob/release-4.6/cluster/examples/kubernetes/ceph/create-external-cluster-resources.py#L226 |