The IBM Spectrum Scale Container Storage Interface (CSI) project enables container orchestrators, such as Kubernetes and OpenShift, to manage the life-cycle of persistent storage.
Apache License 2.0
66
stars
49
forks
source link
driver is giving warnung error as "Unable to retrieve some image pull secrets" on k8s cluster #1138
In driver pod description of 2.11.0 then error is coming as "Unable to retrieve some image pull secrets"
How to Reproduce?
Please list the steps to help development teams reproduce the behavior
Install CSI 2.11.0 GM build :
[root@csi-kube129-1-x-master saurabh]# oc apply -f ibm-spectrum-scale-csi-operator.yaml
deployment.apps/ibm-spectrum-scale-csi-operator created
clusterrole.rbac.authorization.k8s.io/ibm-spectrum-scale-csi-operator created
clusterrolebinding.rbac.authorization.k8s.io/ibm-spectrum-scale-csi-operator created
serviceaccount/ibm-spectrum-scale-csi-operator created
customresourcedefinition.apiextensions.k8s.io/csiscaleoperators.csi.ibm.com created
[root@csi-kube129-1-x-master saurabh]# oc apply -f csiscaleoperators.csi.ibm.com_cr.yaml
csiscaleoperator.csi.ibm.com/ibm-spectrum-scale-csi created
[root@csi-kube129-1-x-master saurabh]# oc get pods
NAME READY STATUS RESTARTS AGE
ibm-spectrum-scale-csi-9wrmw 3/3 Running 0 9s
ibm-spectrum-scale-csi-attacher-797bc6ff85-plgws 1/1 Running 0 9s
ibm-spectrum-scale-csi-attacher-797bc6ff85-rmg75 1/1 Running 0 9s
ibm-spectrum-scale-csi-d6zxv 3/3 Running 0 9s
ibm-spectrum-scale-csi-operator-64bcd4dbd7-zvvcd 1/1 Running 0 52s
ibm-spectrum-scale-csi-provisioner-6dd44f9b4-qjm4j 1/1 Running 0 9s
ibm-spectrum-scale-csi-resizer-5999c8796f-4ms49 1/1 Running 0 9s
ibm-spectrum-scale-csi-snapshotter-5c5d7fbf5b-47zmx 1/1 Running 0 9s
[root@csi-kube129-1-x-master saurabh]# oc get cso
NAME VERSION SUCCESS
ibm-spectrum-scale-csi 2.11.0 True
[root@csi-kube129-1-x-master saurabh]# oc describe pod | grep quay
Image: quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:b2bc343eadbc11d9ed74a8477d2cd0a7a8460a72203d3f6236d4662e68df1166
Normal Pulled 18s kubelet Container image "quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:b2bc343eadbc11d9ed74a8477d2cd0a7a8460a72203d3f6236d4662e68df1166" already present on machine
Image: quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:b2bc343eadbc11d9ed74a8477d2cd0a7a8460a72203d3f6236d4662e68df1166
Normal Pulled 18s kubelet Container image "quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:b2bc343eadbc11d9ed74a8477d2cd0a7a8460a72203d3f6236d4662e68df1166" already present on machine
Image: quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-operator@sha256:bd264199ac10d574163bfa32bb88844fd786ee6f794a56e235591d2f051c7807
CSI_DRIVER_IMAGE: quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:b2bc343eadbc11d9ed74a8477d2cd0a7a8460a72203d3f6236d4662e68df1166
Normal Pulled 61s kubelet Container image "quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-operator@sha256:bd264199ac10d574163bfa32bb88844fd786ee6f794a56e235591d2f051c7807" already present on machine
Check the driver pod description :
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 4m2s default-scheduler Successfully assigned ibm-spectrum-scale-csi-driver/ibm-spectrum-scale-csi-d6zxv to csi-kube129-1-x-worker2.fyre.ibm.com
Warning FailedMount 4m2s kubelet MountVolume.SetUp failed for volume "spectrum-scale-config" : configmap "spectrum-scale-config" not found
Normal Pulled 4m1s kubelet Container image "quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:b2bc343eadbc11d9ed74a8477d2cd0a7a8460a72203d3f6236d4662e68df1166" already present on machine
Normal Created 4m1s kubelet Created container ibm-spectrum-scale-csi
Normal Started 4m1s kubelet Started container ibm-spectrum-scale-csi
Normal Pulled 4m1s kubelet Container image "registry.k8s.io/sig-storage/csi-node-driver-registrar@sha256:c53535af8a7f7e3164609838c4b191b42b2d81238d75c1b2a2b582ada62a9780" already present on machine
Normal Created 4m kubelet Created container driver-registrar
Normal Started 4m kubelet Started container driver-registrar
Normal Pulled 4m kubelet Container image "registry.k8s.io/sig-storage/livenessprobe@sha256:5baeb4a6d7d517434292758928bb33efc6397368cbb48c8a4cf29496abf4e987" already present on machine
Normal Created 4m kubelet Created container liveness-probe
Normal Started 4m kubelet Started container liveness-probe
Warning FailedToRetrieveImagePullSecret 30s (x6 over 4m1s) kubelet Unable to retrieve some image pull secrets (ibm-spectrum-scale-csi-registrykey, ibm-entitlement-key); attempting to pull the image may not succeed.
Describe the bug
In driver pod description of 2.11.0 then error is coming as "Unable to retrieve some image pull secrets"
How to Reproduce?
Please list the steps to help development teams reproduce the behavior
Expected behavior
on k8s env above error log should not come
Logs :