Bootstrap node does not finish, installation does not progress #1727
mcazeneuve
started this conversation in
General
Replies: 2 comments 3 replies
-
Please attach log bundle |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
On a fresh install openshift-install-linux-4.13.0-0.okd-2023-09-03-082426
The bootstrap node does not move forward with the installation. It remains waiting for a process to finish.
Version
openshift-install-linux-4.13.0-0.okd-2023-09-03-082426
UPI install method, Vsphere
How reproducible
100%
Log bundle
journalctl -b -f -u bootkube.service
io.openshift.build.commit.ref=openshift-4.13, io.openshift.expose-services=, io.openshift.build.commit.date=, io.openshift.tags=openshift,base, io.openshift.build.commit.message=, License=GPLv2+)
Sep 06 15:10:18 zn-bts bootkube.sh[655300]: Starting cluster-bootstrap...
Sep 06 15:10:18 zn-bts bootkube.sh[655300]: Waiting for CEO to finish...
Sep 06 15:10:19 zn-bts bootkube.sh[656079]: Error: name "wait-for-ceo" is in use: container already exists
Sep 06 15:10:19 zn-bts podman[656079]: 2023-09-06 15:10:19.021736558 +0000 UTC m=+0.047552096 image pull 03ab13fdb63234058e1f4d89423a6022e722a14202179bdbc7c11bb0b57f34d9 quay.io/openshift/okd-content@sha256:ac0516ca2287bd7535f252665354db21866a265053e4ae3e62d9a1d79c2f6411
Sep 06 15:10:19 zn-bts systemd[1]: bootkube.service: Main process exited, code=exited, status=125/n/a
Sep 06 15:10:19 zn-bts systemd[1]: bootkube.service: Failed with result 'exit-code'.
Sep 06 15:10:19 zn-bts systemd[1]: bootkube.service: Consumed 5.816s CPU time.
Beta Was this translation helpful? Give feedback.
All reactions