-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.19, 4.20, 4.21
-
None
-
Quality / Stability / Reliability
-
True
-
-
None
-
None
-
None
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
vSphere installation is failing during the image unpacking with a “no space left on device” error.This issue is consistently observed in Compact and HA installations, while it occurs intermittently in SNO (Single Node OpenShift) installations.
Version-Release number of selected component (if applicable):
4.19, 4.20, 4.21
How reproducible:
Always
Steps to Reproduce:
1. Create agent ISO
2. Boot the created ISO on vSphere vm's
Actual results:
MESSAGE=E1006 22:28:58.992836 6040 pod_workers.go:1301] "Error syncing pod, skipping" err="[failed to \"StartContainer\" for \"kube-controller-manager\" with ImagePullBackOff: \"Back-off pulling image \\\"quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:4314d3f33ac9e16f8dfab5cdf95844747661d550d4e36546b8716ea5896e4ddc\\\": ErrImagePull: unable to pull image or OCI artifact: pull image err: writing blob: storing blob to file \\\"/var/tmp/container_images_storage979484291/1\\\": write /var/tmp/container_images_storage979484291/1: no space left on device; artifact err: provided artifact is a container image\", failed to \"StartContainer\" for \"cluster-policy-controller\" with CrashLoopBackOff: \"back-off 2m40s restarting failed container=cluster-policy-controller pod=bootstrap-kube-controller-manager-ci-op-7qd07q7l-a131e-master-0_kube-system(37efc67fc88c33fd24f134e445557f49)\"]" pod="kube-system/bootstrap-kube-controller-manager-ci-op-7qd07q7l-a131e-master-0" podUID="37efc67fc88c33fd24f134e445557f49"
Expected results:
The installation should be successful.
VM Configuration:
Memory=16384 CPU=4 Disk Size=120GB