Description of problem (please be detailed as possible and provide log snippets): For an external mode cluster, if the RGW endpoint changes due to a node replacement operation or an issue with the Load balancer(HA proxy) configured for RGW on the RHCS cluster, this will affect the noobaa operations on the OCS cluster. There should be a way, either automatically or through a series of manual steps, to update this change in RGW endpoint in noobaa without having to re-deploy OCS altogether. Version of all relevant components (if applicable): OCS version: 4.5.0-526.ci OCP version: 4.5.0-0.nightly-2020-08-20-051434 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Yes, Noobaa services will get affected Is there any workaround available to the best of your knowledge? Not that I am aware of Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 4 Can this issue reproducible? Yes Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1.If the RHCS cluster has only one RGW endpoint configured, use the endpoint to create an OCS cluster in external mode 2. Perform a node replacement operation on the RGW node. This would change the the RGW endpoint 3. Check noobaa status and services
RFE, not a blocker for 4.5, moving to 4.6. Also, why is it not a BZ on rook ? Rook provides the URL of RGW to connect to, if rook changes but MCG does not, its a bug in MCG. If rook does not change as well, that's the first step.
I think its a rook BZ as rook provides the URL to connect to. What do you think ?
Adding some info (eng. internal :) ) We would need to enable updated to the external connection which is used by this BS and update the node within the hosted_agents process
in any case we are dependent on rook changes (and also ocs-operator due to those changes) that will happen only on 4.7 Moving this to 4.7
A PR was issued with a fix on the upstream project (see link section) The changes in linked PR will guarantee that NooBaa will consume FQDN for RGW service which should also solve the address change problem
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat OpenShift Container Storage 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2041