Description of problem (please be detailed as possible and provide log snippests): MirrorPeer status update stays as ExchangedSecret even if no secret exchange has been done yet. Version of all relevant components (if applicable): 4.9 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Status won't be properly reflected on the MirrorPeer CR Is there any workaround available to the best of your knowledge? N/A Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? Yes Can this issue reproduce from the UI? N/A If this is a regression, please provide more details to justify this: N/A Steps to Reproduce: 1.Setup DR using a hub cluster, 2 managed clusters 2. In the initial phase, when secrets are not exchanged 3. Check MirrorPeer status, peer.status.phase Actual results: It is in ExchangedSecret Expected results: It should be in ExchangingSecret
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 Data Foundation 4.9.0 enhancement, security, and bug fix 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:5086