Note ---- This issue can be observed only after fixing or applying a workaround for BZ#1992231. Description of problem ---------------------- After creating a HostPathProvisioner CustomResource, hostpath-provisioner Pods are stuck in ImagePullBackOff state. > kubectl -n openshift-cnv get pods -l k8s-app=hostpath-provisioner > > NAME READY STATUS RESTARTS AGE > hostpath-provisioner-7dfb4 4/5 ImagePullBackOff 0 9m46s > hostpath-provisioner-dwbgk 4/5 ImagePullBackOff 0 9m46s > hostpath-provisioner-qr2w4 4/5 ImagePullBackOff 0 9m46s They are failing to pull the hostpath-provisioner-csi image. > Warning Failed 69s (x2 over 80s) kubelet Error: ErrImagePull > Warning Failed 69s (x2 over 80s) kubelet Failed to pull image "hostpath-provisioner-csi": rpc error: code = Unknown desc = Error reading manifest latest in docker.io/library/hostpath-provisioner-csi: errors: > denied: requested access to the resource is denied > unauthorized: authentication required > Warning Failed 69s kubelet Error: ImagePullBackOff Analysis -------- Support for CSI has been added to hostpath-provisioner-operator by upstream PR https://github.com/kubevirt/hostpath-provisioner-operator/pull/113. Downstream build chain need to be updated accordingly. Among others: - hostpath-provisioner-csi image needs to be built downstream - CSI_PROVISIONER_IMAGE variable needs to be set to point to this image. Version ------- OCP: 4.9.0-0.nightly CNV: http://cnv-version-explorer.apps.cnv.engineering.redhat.com/BundleDetails?ver=v4.9.0-89
Mitigated for CNV-4.9.0 by https://code.engineering.redhat.com/gerrit/c/hostpath-provisioner-operator/+/264197. Included since http://cnv-version-explorer.apps.cnv.engineering.redhat.com/BundleDetails?ver=v4.9.0-103. Lowering the severity since it will be fully addressed for CNV-v4.10.
The feature should be fully addressed in CNV 4.10, so change the version to 4.10 If the issue can not be reproduced on 4.10, feel free to close it.
the workaround is specific to 4.9, the work for 4.10 is not done yet.
Prefer to track "HPP v4.10 fails to deploy downstream" with a single bug. This bug describes an earlier failure mode that should be resolved by now, too. *** This bug has been marked as a duplicate of bug 1992231 ***