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:
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.
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?
(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?
Not a blocker, moving out.
Since this is not specific to any one operator and an OCP issue, I'm moving it to "unclassified" component. We should probably just close this BZ and track the Jira issue.