You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ journalctl -b -f -u release-image.service -u bootkube.serviceDec 20 14:07:37 serjtk-cluster-9mr5t-bootstrap systemd[1]: bootkube.service: Failed with result 'exit-code'.Dec 20 14:07:37 serjtk-cluster-9mr5t-bootstrap systemd[1]: bootkube.service: Consumed 1.268s CPU time.Dec 20 14:07:42 serjtk-cluster-9mr5t-bootstrap systemd[1]: bootkube.service: Scheduled restart job, restart counter is at 942.Dec 20 14:07:42 serjtk-cluster-9mr5t-bootstrap systemd[1]: Stopped Bootstrap a Kubernetes cluster.Dec 20 14:07:42 serjtk-cluster-9mr5t-bootstrap systemd[1]: bootkube.service: Consumed 1.268s CPU time.Dec 20 14:07:42 serjtk-cluster-9mr5t-bootstrap systemd[1]: Started Bootstrap a Kubernetes cluster.Dec 20 14:07:44 serjtk-cluster-9mr5t-bootstrap bootkube.sh[318202]: F1220 14:07:44.318642 1 image.go:32] error: error: Unknown name requested, could not find cluster-config-api in UpdatePayloadDec 20 14:07:44 serjtk-cluster-9mr5t-bootstrap systemd[1]: bootkube.service: Main process exited, code=exited, status=255/EXCEPTIONDec 20 14:07:44 serjtk-cluster-9mr5t-bootstrap systemd[1]: bootkube.service: Failed with result 'exit-code'.Dec 20 14:07:44 serjtk-cluster-9mr5t-bootstrap systemd[1]: bootkube.service: Consumed 1.228s CPU time.
Anything else we need to know?
do not find cluster-config-api image
$ podman run --quiet --rm --net=none registry.ci.openshift.org/origin/release@sha256:3cdbe4a34d3f32881c7183b4446951d5fd98fb290631cbacb01eaa1e3aecb4b5 image cluster-config-api
F1220 12:37:57.774137 1 image.go:32] error: error: Unknown name requested, could not find cluster-config-api in UpdatePayload
The text was updated successfully, but these errors were encountered:
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
openshift-cibot
added
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Jun 19, 2024
Version
Platform:
libvirt
Please specify:
IPI
What happened?
Bootstrap node do not complete boot
What you expected to happen?
Enter text here.
How to reproduce it (as minimally and precisely as possible)?
#platform libvirt
$ openshift-install create cluster
Anything else we need to know?
do not find cluster-config-api image
$ podman run --quiet --rm --net=none registry.ci.openshift.org/origin/release@sha256:3cdbe4a34d3f32881c7183b4446951d5fd98fb290631cbacb01eaa1e3aecb4b5 image cluster-config-api
F1220 12:37:57.774137 1 image.go:32] error: error: Unknown name requested, could not find cluster-config-api in UpdatePayload
The text was updated successfully, but these errors were encountered: