Bug 1813863
| Summary: | OCP 4.5 fails to get deployed on Vsphere UPI | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Neha Berry <nberry> |
| Component: | Node | Assignee: | Ryan Phillips <rphillips> |
| Status: | CLOSED DUPLICATE | QA Contact: | Sunil Choudhary <schoudha> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.5 | CC: | aos-bugs, ebenahar, jokerman, ocs-bugs, prsurve |
| 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-03-16 20:05:16 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
Neha Berry
2020-03-16 10:36:14 UTC
> Worker machines failed to come up (either 1 or all). As seen in vcenter, all 3 compute nodes for Worker are UP, but they failed to become OCP nodes
time="2020-03-16T07:28:26Z" level=debug msg="Still waiting for the cluster to initialize: Some cluster operators are still updating: authentication, cluster-autoscaler, console, csi-snapshot-controller, ingress, kube-storage-version-migrator, machine-api, monitoring"
time="2020-03-16T07:32:11Z" level=debug msg="Still waiting for the cluster to initialize: Working towards 4.5.0-0.nightly-2020-03-15-220309: 98% complete"
[root@magna012 mar16-dc7]#
The workers are failing to join the cluster, so probably get the node team to look at it.
Mar 16 07:09:48.887942 control-plane-0 crio[1276]: time="2020-03-16 07:09:48.887885286Z" level=error msg="Container creation error: time=\"2020-03-16T07:09:48Z\" level=error msg=\"container_linux.go:349: starting container process caused \\\"exec: \\\\\\\"/manager\\\\\\\": stat /manager: no such file or directory\\\"\"\ncontainer_linux.go:349: starting container process caused \"exec: \\\"/manager\\\": stat /manager: no such file or directory\"\n" Mar 16 07:09:49.054036 control-plane-0 crio[1276]: time="2020-03-16 07:09:49.053982991Z" level=error msg="Container creation error: time=\"2020-03-16T07:09:49Z\" level=error msg=\"container_linux.go:349: starting container process caused \\\"exec: \\\\\\\"/machine-controller-manager\\\\\\\": stat /machine-controller-manager: no such file or directory\\\"\"\ncontainer_linux.go:349: starting container process caused \"exec: \\\"/machine-controller-manager\\\": stat /machine-controller-manager: no such file or directory\"\n" Marking as a duplicate. The installer is using the wrong 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"
*** This bug has been marked as a duplicate of bug 1813026 ***
|