Bug 1845897
| Summary: | OLM Operators cannot be updated to 4.4 from 4.3 channel | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jian Zhang <jiazha> | |
| Component: | OLM | Assignee: | Evan Cordell <ecordell> | |
| OLM sub component: | OLM | QA Contact: | Jian Zhang <jiazha> | |
| Status: | CLOSED NOTABUG | Docs Contact: | ||
| Severity: | urgent | |||
| Priority: | urgent | CC: | anli | |
| Version: | 4.4 | Keywords: | Regression | |
| Target Milestone: | --- | |||
| Target Release: | 4.6.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1846316 (view as bug list) | Environment: | ||
| Last Closed: | 2020-06-15 12:04:03 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: | 1846316 | |||
|
Comment 2
Evan Cordell
2020-06-10 14:28:32 UTC
I hit a similar issue in one OCP 4.5 today. To overcome the re-sync. I had restarted all pods under openshift-marketplace and openshift-operator-lifecycle-manager. But that's helpless. Hi Evan, > Can this be reproduced on a new install of OCP 4.4? No, I cannot reproduce it on a new OCP 4.4 cluster: Cluster version is 4.4.0-0.nightly-2020-06-10-183933 [root@preserve-olm-env data]# oc exec catalog-operator-6956b99d9f-wr6gs -n openshift-operator-lifecycle-manager -- olm --version OLM version: 0.14.2 git commit: 527c5c244437e62952c5e7c9f38ace027be0eab0 [root@preserve-olm-env data]# oc get sub NAME PACKAGE SOURCE CHANNEL sriov sriov-network-operator qe-app-registry 4.4 [root@preserve-olm-env data]# oc get ip NAME CSV APPROVAL APPROVED install-l5nmj sriov-network-operator.4.3.25-202006081335 Automatic true install-tdc86 sriov-network-operator.4.4.0-202006080610 Automatic true [root@preserve-olm-env data]# oc get ip NAME CSV APPROVAL APPROVED install-l5nmj sriov-network-operator.4.3.25-202006081335 Automatic true install-tdc86 sriov-network-operator.4.4.0-202006080610 Automatic true [root@preserve-olm-env data]# oc get csv NAME DISPLAY VERSION REPLACES PHASE elasticsearch-operator.4.4.0-202006080610 Elasticsearch Operator 4.4.0-202006080610 Succeeded sriov-network-operator.4.4.0-202006080610 SR-IOV Network Operator 4.4.0-202006080610 sriov-network-operator.4.3.25-202006081335 Succeeded > catalogsource images are not bumped until the resync for operatorsources (about an hour). I'm afraid not, as I described it in the `Description of problem:` above, it still doesn't work after hours. And, as you can see from the provided cluster above, it still failed now: [root@preserve-olm-env data]# oc get sub NAME PACKAGE SOURCE CHANNEL cluster-logging cluster-logging qe-app-registry 4.4 [root@preserve-olm-env data]# oc get ip NAME CSV APPROVAL APPROVED install-g7xlq clusterlogging.4.2.29-202004140532 Automatic true install-sxc4m clusterlogging.4.3.25-202006081335 Automatic true install-trbhc clusterlogging.4.2.32-202005071706 Automatic true [root@preserve-olm-env data]# oc get csv NAME DISPLAY VERSION REPLACES PHASE clusterlogging.4.3.25-202006081335 Cluster Logging 4.3.25-202006081335 clusterlogging.4.2.32-202005071706 Succeeded elasticsearch-operator.4.3.25-202006081335 Elasticsearch Operator 4.3.25-202006081335 elasticsearch-operator.4.2.32-202005050921 Succeeded That turn out a clusterlogging skiprange bug. So close it. |