Bug 1813026
| Summary: | openshift-machine-config-operator-master-e2e-vsphere tests constantly failing | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Kirsten Garrison <kgarriso> |
| Component: | Cloud Compute | Assignee: | Alberto <agarcial> |
| Cloud Compute sub component: | BareMetal Provider | QA Contact: | Jianwei Hou <jhou> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | urgent | ||
| Priority: | unspecified | CC: | adahiya, cglombek, nberry, rphillips, stbenjam |
| Version: | 4.5 | ||
| 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-08-27 22:35:24 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
Kirsten Garrison
2020-03-12 18:29:55 UTC
Seems to be failing a lot on `Run template e2e-vsphere - e2e-vsphere container setup` in these tests around ~1 hour with "failed to initialize the cluster: Cluster operator machine-api is still updating" if you actually look at the failures, https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1556/pull-ci-openshift-machine-config-operator-master-e2e-vsphere/107https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1552/pull-ci-openshift-machine-config-operator-master-e2e-vsphere/105https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1552/pull-ci-openshift-machine-config-operator-master-e2e-vsphere/104all of them have machine-api failing. if you actually look at the failures, https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1556/pull-ci-openshift-machine-config-operator-master-e2e-vsphere/107 https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1552/pull-ci-openshift-machine-config-operator-master-e2e-vsphere/105 https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1552/pull-ci-openshift-machine-config-operator-master-e2e-vsphere/104 all of them have machine-api failing. *** Bug 1813863 has been marked as a duplicate of this bug. *** For some reason the image is using a docker.io template image, and not the real quay.io release image:
- image: docker.io/openshift/origin-machine-api-operator:v4.0.0
imageID: ""
lastState: {}
name: controller-manager
ready: false
restartCount: 0
started: false
state:
waiting:
message: |
container create failed: time="2020-03-16T08:06:47Z" level=error msg="container_linux.go:349: starting container process caused \"exec: \\\"/manager\\\": stat /manager: no such file or directory\""
container_linux.go:349: starting container process caused "exec: \"/manager\": stat /manager: no such file or directory"
Fixed by https://github.com/openshift/machine-api-operator/commit/5c82b317ea90e153f89f55f7e9c990b8ea41bcec 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' |