Bug 1786471
| Summary: | Unable to Re-install kubevirt-hyperconverged Operator | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Asher Shoshan <ashoshan> | |
| Component: | OLM | Assignee: | Vu Dinh <vdinh> | |
| OLM sub component: | OLM | QA Contact: | Salvatore Colangelo <scolange> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | high | |||
| Priority: | high | CC: | bandrade, bluddy, cnv-qe-bugs, ecordell, fdeutsch, mbukatov, ncredi, pbalogh, stirabos, talayan, vdinh, ycui | |
| Version: | 4.3.0 | Flags: | ashoshan:
needinfo-
|
|
| Target Milestone: | --- | |||
| Target Release: | 4.4.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1803135 (view as bug list) | Environment: | ||
| Last Closed: | 2020-05-04 11:21:35 UTC | 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1803135 | |||
|
Description
Asher Shoshan
2019-12-25 14:33:19 UTC
@Asher can you please try a different operator maybe it is a market place bug? Probably it will happen with other operators. IMHO, the root cause of this behaviour is the flaky command: "oc get packagemanifest" From time to time it will not show the package (kubevirt-hyperconverged). See the other BZ, of arbitrary showing only from one catalogSource. Reinstallation is not a primary path. thus omving it out to 2.3 for now. It also looks to be like an OLM or marketplace bug. Agree (OLM issue) - what category to put? It happens on other operator as well (see comment #2) moving to OLM please feel free to change if this is not the correct component Hi, I'm unable to reproduce this issue on 4.3 and 4.4 cluster. I can't reproduce with other operators either. On 4.3, I can only see 2.1.0 version of HCO so I'm unable to test 2.2.0 version that you listed in this BZ. If this issue only happens with HCO 2.2.0, then I suspect this is not an issue coming from OLM or marketplace. Thanks, Vu (In reply to Vu Dinh from comment #8) > Hi, > > I'm unable to reproduce this issue on 4.3 and 4.4 cluster. I can't reproduce > with other operators either. On 4.3, I can only see 2.1.0 version of HCO so > I'm unable to test 2.2.0 version that you listed in this BZ. If this issue > only happens with HCO 2.2.0, then I suspect this is not an issue coming from > OLM or marketplace. > > Thanks, > Vu Hi, Try add some new operatorSource/catalogSource (redhat-operators-stage or rh-verified-operators) which has the product "kubevirt-hyperconverged" or any. Then: 1. oc -n openshift-marketplace get packagemanifests |grep kubevirt --> you'll see only one line from an arbitrary (last?) catalogSource (should be at least two lines one from redhat-operators, and one from the added catalog - this is another BZ). 2. Delete the opsrc created at [1] --> oc -n openshift-marketplace delete opsrc <redhat-operators-stage/rh-verified-operators> 3. repeat [1] --> you won't see the product at all (and not in UI of course). To restore back, I found a WA, by deleting opsrc redhat-operators (which is recreated immediately), after a while you'll see the product again from redhat-operators. *** Bug 1802089 has been marked as a duplicate of this bug. *** Since BZ 1802089 has been closed as a duplicate of this one, adding OCS as Dependent Product here. Hi , Version-Release number of selected component (if applicable): 2.2.0 Steps executed: 1. Instal HCO 2. Uninstall HCO via UI 3. Try re-Install HCO via UI Actual results: HCO FOUND in operator-hub LGMT Additional info: [scolange@scolange ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.3.0-0.nightly-2020-02-17-205936 True False Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581 |