Open
Description
Describe the bug
When we edit secret with wrong user and then check cso status then it is shown as true and there is no event for same
How to Reproduce?
Please list the steps to help development teams reproduce the behavior
- Install CSI with feature to support password rotation #1130 images or dev images:
[root@csi-kube129-1-x-master 1130]# 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 1130]# oc apply -f csiscaleoperators.csi.ibm.com_cr.yaml
csiscaleoperator.csi.ibm.com/ibm-spectrum-scale-csi created
[root@csi-kube129-1-x-master 1130]# oc get pods
NAME READY STATUS RESTARTS AGE
ibm-spectrum-scale-csi-78694 3/3 Running 0 45s
ibm-spectrum-scale-csi-attacher-797bc6ff85-7fhhp 1/1 Running 0 45s
ibm-spectrum-scale-csi-attacher-797bc6ff85-zfhsp 1/1 Running 0 45s
ibm-spectrum-scale-csi-lfffd 3/3 Running 0 45s
ibm-spectrum-scale-csi-operator-6dd75b845f-sdm8p 1/1 Running 0 83s
ibm-spectrum-scale-csi-provisioner-6dd44f9b4-r2wxx 1/1 Running 0 45s
ibm-spectrum-scale-csi-resizer-5999c8796f-fkxsr 1/1 Running 0 45s
ibm-spectrum-scale-csi-snapshotter-5c5d7fbf5b-xg2t2 1/1 Running 0 45s
[root@csi-kube129-1-x-master 1130]# oc get cso
NAME VERSION SUCCESS
ibm-spectrum-scale-csi 2.11.0 True
[root@csi-kube129-1-x-master 1130]# oc describe pod | grep quay
Image: quay.io/badri_pathak/ibm-spectrum-scale-csi-driver:passwordrotation_test12
Normal Pulled 54s kubelet Container image "quay.io/badri_pathak/ibm-spectrum-scale-csi-driver:passwordrotation_test12" already present on machine
Image: quay.io/badri_pathak/ibm-spectrum-scale-csi-driver:passwordrotation_test12
Normal Pulled 54s kubelet Container image "quay.io/badri_pathak/ibm-spectrum-scale-csi-driver:passwordrotation_test12" already present on machine
Image: quay.io/badri_pathak/ibm-spectrum-scale-csi-operator:passwordrotation_test10
CSI_DRIVER_IMAGE: quay.io/badri_pathak/ibm-spectrum-scale-csi-driver:passwordrotation_test12
Normal Pulled 92s kubelet Container image "quay.io/badri_pathak/ibm-spectrum-scale-csi-operator:passwordrotation_test10" already present on machine
- Change gui user with wrong username (here I am changing user to wronguser) with base64:
[root@csi-kube129-1-x-master 1130]# oc edit secret guisecret
secret/guisecret edited
- Check the CSI pods :
[root@csi-kube129-1-x-master 1130]# oc get pods
NAME READY STATUS RESTARTS AGE
ibm-spectrum-scale-csi-78694 3/3 Running 0 3m13s
ibm-spectrum-scale-csi-attacher-797bc6ff85-7fhhp 1/1 Running 0 3m13s
ibm-spectrum-scale-csi-attacher-797bc6ff85-zfhsp 1/1 Running 0 3m13s
ibm-spectrum-scale-csi-lfffd 3/3 Running 0 3m13s
ibm-spectrum-scale-csi-operator-6dd75b845f-sdm8p 1/1 Running 0 3m51s
ibm-spectrum-scale-csi-provisioner-6dd44f9b4-r2wxx 1/1 Running 0 3m13s
ibm-spectrum-scale-csi-resizer-5999c8796f-fkxsr 1/1 Running 0 3m13s
ibm-spectrum-scale-csi-snapshotter-5c5d7fbf5b-xg2t2 1/1 Running 0 3m13s
- Check the CSO status
[root@csi-kube129-1-x-master saurabh]# oc get cso
NAME VERSION SUCCESS
ibm-spectrum-scale-csi 2.11.0 True
Expected behavior
CSO status should be false if username is wrong as improvement so that it will be easy to detect and won't cause any issue during volume creation or CSI upgrade or there should be event generated for the same
logs :
/scale-csi/D.1146
csisnap.tar.gz
Metadata
Metadata
Assignees
Labels
(3) Reduction of function. Significant impact to workload.(3) Issue occurs in normal path but specific limited timing window, or other mitigating factorFor Bug issues to identify what release level issue was found in 2.12.0Indicates that the issue is critical and must be addressed before milestone.Indicates issue is an undesired behavior, usually caused by code error.