Bug 2294400

Summary:	[MDR] left over PVC failed the failover without error
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	dalia <dafrank>
Component:	odf-dr	Assignee:	Nir Soffer <nsoffer>
odf-dr sub component:	ramen	QA Contact:	krishnaram Karthick <kramdoss>
Status:	ASSIGNED ---	Docs Contact:
Severity:	unspecified
Priority:	low	CC:	kseeger, muagarwa, nsoffer
Version:	4.16
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description dalia 2024-06-26 15:00:40 UTC

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:

Comment 7 Sunil Kumar Acharya 2024-06-28 12:12:05 UTC

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.