Bug 1808419
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: | unspecified | ||
Priority: | unspecified | CC: | ecordell |
Version: | 4.4 | ||
Target Milestone: | --- | ||
Target Release: | 4.3.z | ||
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-03-24 14:34:23 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: | 1808418 | ||
Bug Blocks: | 1808422 |
Description
Ben Luddy
2020-02-28 13:42:41 UTC
My apologies posted the comment in the wrong bug. Here is the verification of this one. 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.3.0-0.nightly-2020-03-12-085147 oc get clusteroperators | grep "operator-lifecycle-manager*" operator-lifecycle-manager 4.3.0-0.nightly-2020-03-12-085147 True False False 17h operator-lifecycle-manager-catalog 4.3.0-0.nightly-2020-03-12-085147 True False False 17h operator-lifecycle-manager-packageserver 4.3.0-0.nightly-2020-03-12-085147 True False False 17h oc get pods -n openshift-operator-lifecycle-manager NAME READY STATUS RESTARTS AGE catalog-operator-7db788c658-gjdw7 1/1 Running 0 17h olm-operator-68dd7d597f-wpd7j 1/1 Running 0 17h packageserver-f9cfd58dd-4m9st 1/1 Running 0 17h packageserver-f9cfd58dd-vkxh4 1/1 Running 0 17h 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:0858 |