Bug 2208280

Summary:	[OCP tracker][RDR] Subscription already exists error is seen while installing ODF/MCO operator
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Aman Agrawal <amagrawa>
Component:	odf-dr	Assignee:	umanga <uchapaga>
odf-dr sub component:	multicluster-orchestrator	QA Contact:	krishnaram Karthick <kramdoss>
Status:	ASSIGNED ---	Docs Contact:
Severity:	low
Priority:	unspecified	CC:	muagarwa, odf-bz-bot, uchapaga
Version:	4.13	Keywords:	Regression
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 Aman Agrawal 2023-05-18 13:26:51 UTC

Description of problem (please be detailed as possible and provide log
snippests):
When installing MCO operator for the 1st time on a fresh new cluster, subscription already exists error is seen though it proceeds with the installation.

Version of all relevant components (if applicable):
ODF 4.13.0-201.stable


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Install MCO operator on OCP 4.13
2.
3.


Actual results: Subscription already exists error is seen while installing MCO operator


Expected results: As installtion is being done on a fresh new setup, the error shouldn't be seen.


Additional info:

Comment 3 umanga 2023-05-23 12:13:12 UTC

Need more info on where and when we see the error and the logs.
What's the exact version of OCP 4.13?
If everything works even after the error, it's not a blocker at least.

Comment 12 Mudit Agarwal 2023-08-11 15:37:26 UTC

Hi Aman,

Thanks for providing the steps to the OCP team.
The thing I don't understand is, how is this related to only internal builds and if let's say that is the case then why to fix it because we will not hit this issue in the field?

Comment 13 Aman Agrawal 2023-08-14 08:04:07 UTC

(In reply to Mudit Agarwal from comment #12)
> Hi Aman,
> 
> Thanks for providing the steps to the OCP team.
> The thing I don't understand is, how is this related to only internal builds
> and if let's say that is the case then why to fix it because we will not hit
> this issue in the field?

I haven't tested so not sure if we hit the issue on GA'ed build or not. @kramdoss, is it possible to ask someone to take it up and then decide/close it?