Bug 1728639 - 4.2 nightly payload installation always met "failed to initialize the cluster: Cluster operator operator-lifecycle-manager-packageserver is still updating"
Summary: 4.2 nightly payload installation always met "failed to initialize the cluster...
Keywords:
Status: CLOSED DUPLICATE of bug 1728223
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2.0
Assignee: Evan Cordell
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On:
Blocks: 1726370
TreeView+ depends on / blocked
 
Reported: 2019-07-10 10:44 UTC by Xingxing Xia
Modified: 2019-07-11 01:34 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-11 01:34:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Xingxing Xia 2019-07-10 10:44:08 UTC 
Description of problem:
4.2 nightly payload installation always met "failed to initialize the cluster: Cluster operator operator-lifecycle-manager-packageserver is still updating"

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-07-10-062553
...
4.2.0-0.nightly-2019-07-09-024603 etc.

How reproducible:
Always

Steps to Reproduce:
1. Install IPI env with latest 4.2 nightly payload
2.
3.

Actual results:
1. Always met above error, see the installation log: https://openshift-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Launch%20Environment%20Flexy/63240/console :
...
level=debug msg="Still waiting for the cluster to initialize: Working towards 4.2.0-0.nightly-2019-07-09-024603: 99% complete"
level=debug msg="Still waiting for the cluster to initialize: Working towards 4.2.0-0.nightly-2019-07-09-024603: 99% complete, waiting on authentication, operator-lifecycle-manager-packageserver"
level=debug msg="Still waiting for the cluster to initialize: Working towards 4.2.0-0.nightly-2019-07-09-024603: 99% complete, waiting on authentication, operator-lifecycle-manager-packageserver"
level=debug msg="Still waiting for the cluster to initialize: Some cluster operators are still updating: authentication, operator-lifecycle-manager-packageserver"
level=debug msg="Still waiting for the cluster to initialize: Working towards 4.2.0-0.nightly-2019-07-09-024603: 100% complete, waiting on operator-lifecycle-manager-packageserver"
level=debug msg="Still waiting for the cluster to initialize: Cluster operator operator-lifecycle-manager-packageserver is still updating"
level=fatal msg="failed to initialize the cluster: Cluster operator operator-lifecycle-manager-packageserver is still updating"


Expected results:
1. Success

Additional info:
https://openshift-release.svc.ci.openshift.org/releasestream/4.2.0-0.nightly/release/4.2.0-0.nightly-2019-07-10-062553 , click "aws Failed" link (
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.2/137 job) also met the error
Comment 1 Xingxing Xia 2019-07-10 10:48:16 UTC 
Blocks bug/story testings that require latest 4.2 night payload
Comment 2 Jian Zhang 2019-07-11 01:34:02 UTC 
This is an expected status since one of OLM pods crashed, close it. Feel free to reopen it if you have other concerns. Thanks!
```
mac:bugs jianzhang$ oc get pods -n openshift-operator-lifecycle-manager 
NAME                                READY   STATUS             RESTARTS   AGE
catalog-operator-5664b99598-krd85   1/1     Running            0          24h
olm-operator-654c658467-vnf7h       1/1     Running            0          24h
olm-operators-fq7mb                 0/1     CrashLoopBackOff   292        24h

*** This bug has been marked as a duplicate of bug 1728223 ***
Note You need to log in before you can comment on or make changes to this bug.