Hi Aman, Do you still have the Cluster, If yes can I can see the full error which appeared. It looks like that there is a problem with the operatorGroup. But I can not see the full error from the screenshot attached.
Hi Aman, I also hit the same when I was trying this out. The error was seen just for fraction of a second and resolved itself. It was too instant that I can not even take a screenshot. I believe that this was there even in the ocs-operator and other operators which does support single namespace installation. As far as I understand this after talking to OLM dev console does create these resources for us which just takes time and once created it is resolved and succeeded. Moreover, this is beyond our control and can be fixed in the console itself. I would like to close this. Pls, do let me know if you have any objections.
It should be management console instead of `Console Storage Plugin`
*** This bug has been marked as a duplicate of bug 2002856 ***
Hi Aman, yes both of these bugs are raised at different point of time, but both are targeting the same version of OCP, which is 4.9. Also the fix for https://bugzilla.redhat.com/show_bug.cgi?id=2002856 is handling with these cases where the error message appears for a split of a second, upon installation of an operator(not just ODF, but any). The message seen on the UI might be different but its shown for the same reason, which is a race issue, cause the form is still being evaluated while its being submitted, and the necessary resources are being created. Please let me know if there is anything else I could assist with, otherwise I will close the BZ.
Since https://bugzilla.redhat.com/show_bug.cgi?id=2002856, which is a 4.9 fix of this issue, got merged, Im setting this BZ to ON_QA to get verified.
Checked on ocp 4.9 cluster with payload 4.9.0-0.nightly-2021-11-06-034743, on the installation page of odf-operation page, there is no error info shown up, refer to the attachment.
OCP is no longer using Bugzilla and this bug appears to have been left in an orphaned state. If the bug is still relevant, please open a new issue in the OCPBUGS Jira project: https://issues.redhat.com/projects/OCPBUGS/summary