Description of problem: Steps to Reproduce: 1. Install a cluster on OpenStack with Manila (and get Manila CSI driver as part of it) 2. Check CSI driver pods: oc -n openshift-manila-csi-driver get pod -o wide 3. Create a pod on a master that uses PVC. Actual results: 2. CSI driver pods run only on worker nodes ... openstack-manila-csi-nodeplugin-fhp84 2/2 Running 0 111m 10.0.129.216 jsafrane-f2wz8-worker-cr6hb <none> <none> openstack-manila-csi-nodeplugin-jrqlx 2/2 Running 0 111m 10.0.130.178 jsafrane-f2wz8-worker-h2xrh <none> <none> openstack-manila-csi-nodeplugin-ttggp 2/2 Running 0 111m 10.0.128.232 jsafrane-f2wz8-worker-wxvzf <none> <none> csi-nodeplugin-nfsplugin-6lg6s 1/1 Running 0 111m 10.0.130.178 jsafrane-f2wz8-worker-h2xrh <none> <none> csi-nodeplugin-nfsplugin-tc75g 1/1 Running 0 111m 10.0.128.232 jsafrane-f2wz8-worker-wxvzf <none> <none> csi-nodeplugin-nfsplugin-v2ljx 1/1 Running 0 111m 10.0.129.216 jsafrane-f2wz8-worker-cr6hb <none> <none> ... 3. Masters can't use a PVC provided by the CSI driver Expected results: 2. Even masters have both manila-csi-nodeplugin and manila-csi-nodeplugin driver pods 3. Masters can use a PVC provided by the CSI driver
Verified pass $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.0-0.nightly-2020-08-12-071533 True False 15m Cluster version is 4.6.0-0.nightly-2020-08-12-071533 $ oc get node NAME STATUS ROLES AGE VERSION wduan0812d-2nxng-master-0 Ready master 38m v1.19.0-rc.2+edbf229-dirty wduan0812d-2nxng-master-1 Ready master 38m v1.19.0-rc.2+edbf229-dirty wduan0812d-2nxng-master-2 Ready master 39m v1.19.0-rc.2+edbf229-dirty wduan0812d-2nxng-worker-554xm Ready worker 29m v1.19.0-rc.2+edbf229-dirty wduan0812d-2nxng-worker-6f992 Ready worker 25m v1.19.0-rc.2+edbf229-dirty wduan0812d-2nxng-worker-n4b5h Ready worker 27m v1.19.0-rc.2+edbf229-dirty $ oc -n openshift-manila-csi-driver get pod -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES csi-nodeplugin-nfsplugin-6wqtk 1/1 Running 0 27m 192.168.2.12 wduan0812d-2nxng-master-1 <none> <none> csi-nodeplugin-nfsplugin-8lwqw 1/1 Running 0 27m 192.168.1.232 wduan0812d-2nxng-master-2 <none> <none> csi-nodeplugin-nfsplugin-9h8gz 1/1 Running 0 27m 192.168.3.115 wduan0812d-2nxng-master-0 <none> <none> csi-nodeplugin-nfsplugin-bx8zd 1/1 Running 0 27m 192.168.2.98 wduan0812d-2nxng-worker-554xm <none> <none> csi-nodeplugin-nfsplugin-jcnkx 1/1 Running 0 27m 192.168.1.216 wduan0812d-2nxng-worker-n4b5h <none> <none> csi-nodeplugin-nfsplugin-n6lq8 1/1 Running 0 25m 192.168.0.40 wduan0812d-2nxng-worker-6f992 <none> <none> openstack-manila-csi-controllerplugin-7f48d9c8ff-fb58k 4/4 Running 0 9m32s 10.128.2.10 wduan0812d-2nxng-worker-n4b5h <none> <none> openstack-manila-csi-nodeplugin-8b5c7 2/2 Running 0 27m 192.168.2.12 wduan0812d-2nxng-master-1 <none> <none> openstack-manila-csi-nodeplugin-9xpqq 2/2 Running 0 27m 192.168.1.216 wduan0812d-2nxng-worker-n4b5h <none> <none> openstack-manila-csi-nodeplugin-b5s6t 2/2 Running 0 25m 192.168.0.40 wduan0812d-2nxng-worker-6f992 <none> <none> openstack-manila-csi-nodeplugin-dhjfl 2/2 Running 0 27m 192.168.2.98 wduan0812d-2nxng-worker-554xm <none> <none> openstack-manila-csi-nodeplugin-fjnxz 2/2 Running 0 27m 192.168.1.232 wduan0812d-2nxng-master-2 <none> <none> openstack-manila-csi-nodeplugin-hcn2d 2/2 Running 0 27m 192.168.3.115 wduan0812d-2nxng-master-0 <none> <none>
Make sure the pod cound be running on master. $ oc get pod -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES mypod04 1/1 Running 0 102s 10.130.0.31 wduan0812d-2nxng-master-0 <none> <none> $ oc get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE mypvc04 Bound pvc-4671eea4-53b7-4ab1-bd37-b2c31e4b2dca 4Gi RWX csi-manila-ceph 113s
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196