Bug 1808418
Summary: | If OLM catalog operator cannot reach the API server, it does not seem to retry | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Ben Luddy <bluddy> |
Component: | OLM | Assignee: | Ben Luddy <bluddy> |
OLM sub component: | OLM | QA Contact: | Bruno Andrade <bandrade> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | bandrade, kuiwang, scolange, yhui |
Version: | 4.4 | ||
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: | Environment: | ||
Last Closed: | 2020-05-04 11:43:34 UTC | Type: | --- |
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: | 1807128 | ||
Bug Blocks: | 1808419 |
Description
Ben Luddy
2020-02-28 13:36:44 UTC
Installed cluster and left it installed for approximately one day and OLM Cluster Operators are running as expected. Marking as VERIFIED. OCP Cluster Version: 4.4.0-0.nightly-2020-03-03-110909 oc get clusteroperators | grep "operator-lifecycle-manager*" operator-lifecycle-manager 4.4.0-0.nightly-2020-03-03-110909 True False False 23h operator-lifecycle-manager-catalog 4.4.0-0.nightly-2020-03-03-110909 True False False 23h operator-lifecycle-manager-packageserver 4.4.0-0.nightly-2020-03-03-110909 True False False 23h oc get pods -n openshift-operator-lifecycle-manager NAME READY STATUS RESTARTS AGE catalog-operator-79fd684bbd-jfftt 1/1 Running 0 9h olm-operator-7796cb5d6c-5mk8w 1/1 Running 0 9h packageserver-75f9d47c9-65tlk 1/1 Running 0 9h packageserver-75f9d47c9-99nhg 1/1 Running 0 9h 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 |