Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 1744796 [details] both 2.6 and 2.5 operator available at first Description of problem: Both CNV 2.5.2 operator and CNV 2.6.0 operator are in operatorHub at first, but CNV 2.5.2 is gone after some time. I did a lots of uninstall and install during the time, not sure whether it's the cause. Version-Release number of selected component (if applicable): 100% How reproducible: Steps to Reproduce: 1. Navigate to operatorHub in OCP console 2. Inputs 'Openshift Virt' to filter operators 3. Install/uninstall CNV for several times Actual results: CNV 2.5.2 operator is not available operatorHub Expected results: CNV 2.5.2 operator is always available operatorHub Additional info:
Created attachment 1744797 [details] cnv 2.5 is not available after some time
Which version of OCP are you using?
(In reply to Inbar Rose from comment #2) > Which version of OCP are you using? OCP 4.7.0-fc.1
CNV 2.5.2 operator come back again after some time, I think I've reported the same issue before, will find that issue.
(In reply to Guohua Ouyang from comment #6) > CNV 2.5.2 operator come back again after some time, I think I've reported > the same issue before, will find that issue. The similar issue https://bugzilla.redhat.com/show_bug.cgi?id=1851798 was fixed. The symptom is: CNV 2.5.2 operator disappears at some time and appears again at some time.
(In reply to Guohua Ouyang from comment #7) > The similar issue https://bugzilla.redhat.com/show_bug.cgi?id=1851798 was > fixed. I tend to agree that this is just a different effect related to the same root cause (a single operator can be, even just temporarily, retrieved from two different catalog sources generating a clash in the packagemanifest and so on the UI. 1851798 didn't really got fixed but simply marked as a duplicate of https://bugzilla.redhat.com/1814822 which is neither fixed but simply deferred to OCP 4.8. On our side, the best we can do is double check our install and uninstall scripts to prevent any clash on the packagemanifest between different test round. *** This bug has been marked as a duplicate of bug 1814822 ***