Bug 1825512
Summary: | v1 CRDs are not supported by CVO | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Evan Cordell <ecordell> |
Component: | Cluster Version Operator | Assignee: | Evan Cordell <ecordell> |
Status: | CLOSED ERRATA | QA Contact: | liujia <jiajliu> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 4.5 | CC: | aos-bugs, jokerman |
Target Milestone: | --- | ||
Target Release: | 4.5.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-07-13 17:28: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: |
Description
Evan Cordell
2020-04-18 17:17:28 UTC
Failed e2e log is here. https://gcsweb-ci.svc.ci.openshift.org/gcs/origin-ci-test/pr-logs/pull/operator-framework_operator-lifecycle-manager/1453/pull-ci-operator-framework-operator-lifecycle-manager-master-e2e-aws-olm/5047/artifacts/e2e-aws-olm/installer/ OLM shipped v1 CRD in v4.5 which should be supported in CVO. Will check the latest e2e job to verify the bug. The issue has not occurred in the latest e2e job against pr1453. https://storage.googleapis.com/origin-ci-test/pr-logs/pull/operator-framework_operator-lifecycle-manager/1453/pull-ci-operator-framework-operator-lifecycle-manager-master-e2e-aws-olm/5085/artifacts/e2e-aws-olm/installer/.openshift_install.log time="2020-04-19T15:11:01Z" level=info msg="API v1.18.0-rc.1 up" time="2020-04-19T15:11:01Z" level=info msg="Waiting up to 40m0s for bootstrapping to complete..." time="2020-04-19T15:19:34Z" level=debug msg="Bootstrap status: complete" time="2020-04-19T15:19:34Z" level=info msg="Destroying the bootstrap resources..." ... time="2020-04-19T15:21:01Z" level=info msg="Waiting up to 30m0s for the cluster at https://api.ci-op-1yqlkmk7-0af52.origin-ci-int-aws.dev.rhcloud.com:6443 to initialize..." time="2020-04-19T15:21:02Z" level=debug msg="Still waiting for the cluster to initialize: Working towards 0.0.1-2020-04-19-150125: 75% complete" time="2020-04-19T15:21:28Z" level=debug msg="Still waiting for the cluster to initialize: Working towards 0.0.1-2020-04-19-150125: 76% complete" time="2020-04-19T15:21:43Z" level=debug msg="Still waiting for the cluster to initialize: Working towards 0.0.1-2020-04-19-150125: 82% complete" time="2020-04-19T15:21:58Z" level=debug msg="Still waiting for the cluster to initialize: Working towards 0.0.1-2020-04-19-150125: 83% complete" time="2020-04-19T15:22:13Z" level=debug msg="Still waiting for the cluster to initialize: Working towards 0.0.1-2020-04-19-150125: 85% complete" time="2020-04-19T15:23:13Z" level=debug msg="Still waiting for the cluster to initialize: Working towards 0.0.1-2020-04-19-150125: 86% complete, waiting on authentication, console, csi-snapshot-controller, image-registry, ingress, kube-storage-version-migrator, monitoring" time="2020-04-19T15:26:28Z" level=debug msg="Still waiting for the cluster to initialize: Working towards 0.0.1-2020-04-19-150125: 86% complete, waiting on authentication, console, monitoring" time="2020-04-19T15:30:13Z" level=debug msg="Still waiting for the cluster to initialize: Working towards 0.0.1-2020-04-19-150125: 87% complete, waiting on authentication" time="2020-04-19T15:32:13Z" level=debug msg="Still waiting for the cluster to initialize: Working towards 0.0.1-2020-04-19-150125: 98% complete" time="2020-04-19T15:32:28Z" level=debug msg="Cluster is initialized" 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:2409 |