Created attachment 2038279 [details] Discovered App status dashboard with message to cleanup resources Description of problem (please be detailed as possible and provide log snippests): When Failover is initiated the new Discovered app status panel tells the user they need to delete the application on the cluster they are failing over from WHEN the DRPC Progression is stuck at WaitForReadiness vs WaitOnUserToCleanUp. Reference attached diagrams. Version of all relevant components (if applicable): OCP - 4.16.0-ec.6 ODF - 4.16.0-129 ACM - 2.10.3 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? If application is deleted before DRPC progression WaitOnUserToCleanUp based on the wrong instructions in the Discovered app UI then the application will not be able to be recovered. Is there any workaround available to the best of your knowledge? No. Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 3 Can this issue reproducible? Yes Can this issue reproduce from the UI? Yes If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Create RDR test env 2. Create app on one of the managed clusters without using ACM 3. Using Discovered app UI assign DR policy and wait for PV replication and kube-object backups to be Healthy in Discovered apps status dashboard. 4. Initiate Failover Actual results: Message in Discovered apps UI tells user to delete app on cluster failing over from BEFORE WaitOnUserToCleanUp DRPC progression is present. Expected results: Message in Discovered apps UI tells user to delete app on cluster failing over from AFTER WaitOnUserToCleanUp DRPC progression is present. Additional info:
Currently UI display this message only when DRPC `status.phase` reports it to be as "FailedOver" and `status.conditions` reports "Available" as true. We could add more checks on DRPC progression (WaitForReadiness & WaitOnUserToCleanUp), but might need UX inputs on what messages to display in between. Since we are already in 4.16.0 RC phase and this doesn't seems to me like a release blocker, I am moving this to 4.16.z release. Annette, if needed, can we add this to the documentation instead, until we fix it in the z-stream (or next release).
@skatiyar I do not see adding this to the documentation for 4.16.0. This becomes an issue if the Failover (failover not working correctly) gets stuck in a DRPC progression other than WaitOnUserToCleanUp.
(In reply to Annette Clewett from comment #5) > This becomes an issue if the Failover (failover not working > correctly) gets stuck in a DRPC progression other than WaitOnUserToCleanUp. Is it an edge case (given DRPC phase is already reported as "FailedOver" ^^) or it can happen quite often ?? ^^ I can see here: https://github.com/red-hat-storage/ramen/blob/main/api/v1alpha1/drplacementcontrol_types.go#L53-L55, "FailedOver, state recorded in the DRPC status when the failover process has completed" If latter and we absolutely need to fix it in "4.16.0" itself (not z-stream), then we need to raise this bug as a release blocker (we are already past blocker bugs fixing phase).
Please update the RDT flag/text appropriately.
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 (Important: Red Hat OpenShift Data Foundation 4.17.0 Security, Enhancement, & 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-2024:8676