Description of problem (please be detailed as possible and provide log snippests): We had a leftover PVC on the scondry cluster due to this bug https://bugzilla.redhat.com/show_bug.cgi?id=2291343 After applying the workaround, tried to failover the same application, but it didn't work, the PVC was there but the VM/pod were not. Version of all relevant components (if applicable): 4.16 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? No Is there any workaround available to the best of your knowledge? yes, delete the PVC 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. Have a PVC on secondry cluster that match by name/namespace to the one on the primary 2. Failover primary cluster 3. Check if failover succeeded Actual results: failover failed without any indication of why Expected results: Some sort of error (resource already exist in the secondry cluster) Additional info:
Moving the non-blocker BZ out of ODF-4.16.0. If this is a blocker feel free to propose it back with justification note.