Description of problem (please be detailed as possible and provide log snippests): On a RDR setup, when an application is deleted while the "VolumeSynchronizationDelay" alert is being fired, the alert continues to be displayed in the UI even after the application is deleted. Version of all relevant components (if applicable): OCP: 4.15.0-0.nightly-2024-02-14-214710 ODF: 4.15.0-142.stable ACM: 2.9.2 Submariner: 0.16.3 VolSync: 0.8.0 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? User impact: Users might be confused by the presence of an alert for a non-existent application. 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)? 1 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. Deploy RDR setup and enable basic monitoring 2. Create an application set based application 3. Wait for VolumeSynchronizationDelay critical alert to appear in the UI. 4. While the alert is being fired, delete the application via UI (ensure option "Remove ApplicationSet related resources" is selected during deletion). 5. Verify Application resources are deleted along with automatic deletion of DRPC from hub cluster 6. Observe that the alert remains visible in the UI despite the application being gone. Actual results: VolumeSynchronizationDelay alert incorrectly persists in UI despite application deletion Expected results: VolumeSynchronizationDelay alert should not be fired incorrectly after application deletion Additional info:
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.16.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:4591