Hello.
I’ve just installed Portworx 2.9.1.3 (for CP4D) on our internal Baremetal OCP4.10 cluster with the file “CP4D_ENT_ED_Portworx_2.9.1.3.tgz”. “pxctl status” command says that it’s operational,but all of stork scheduler pods fail to start up due to “ImagePullBackoff” error as below:
[root@ilab081062 work]# oc get pod
NAME READY STATUS RESTARTS AGE
portworx-api-d6bsm 1/1 Running 0 49m
portworx-api-s9hg2 1/1 Running 0 49m
portworx-api-z4wnl 1/1 Running 0 49m
portworx-kvdb-66rlr 1/1 Running 0 45m
portworx-kvdb-hxntf 1/1 Running 0 45m
portworx-kvdb-w6bvv 1/1 Running 0 45m
portworx-operator-69b78b9cdd-cn56b 1/1 Running 0 54m
px-csi-ext-69b86bbc99-5pt85 3/3 Running 0 49m
px-csi-ext-69b86bbc99-t5gtk 3/3 Running 0 49m
px-csi-ext-69b86bbc99-v2dhw 3/3 Running 0 49m
px-storage-cluster-646p2 2/2 Running 0 49m
px-storage-cluster-8scp4 2/2 Running 0 49m
px-storage-cluster-ssxct 2/2 Running 0 49m
stork-65b574fb9b-4crwq 1/1 Running 0 49m
stork-65b574fb9b-5cpfl 1/1 Running 0 49m
stork-65b574fb9b-s5zbr 1/1 Running 0 49m
stork-scheduler-7c9c9d99bf-j74m7 0/1 ImagePullBackOff 0 49m
stork-scheduler-7c9c9d99bf-ppmgm 0/1 ImagePullBackOff 0 44m
stork-scheduler-7c9c9d99bf-x8zhh 0/1 ImagePullBackOff 0 49m
The result of “oc describe pod” command shows that it’s requesting the image “kube-scheduler-amd64:v1.21.4”, but the zip file doesn’t contain the image (instead kube-scheduler-amd64:v1.21.1 is included in it).
How can I get v1.21.4 image?
Warning Failed 18m (x4 over 20m) kubelet Failed to pull image “ilab081062.lab.japan.ibm.com:5000/kube-system/kube-scheduler-amd64:v1.21.4”: rpc error: code = Unknown desc = reading manifest v1.21.4 in ilab081062.lab.japan.ibm.com:5000/kube-system/kube-scheduler-amd64: manifest unknown: manifest unknown