Unsolved
7 Posts
0
889
September 16th, 2020 12:00
Powermax 1.4 driver and volume expansion
We noticed the powermax CSI driver had updated to 1.4 on github and deployed it. Per the document, the allow volume expansion is supposed to be true by default. We did not find that to be the case. Additionally, even though we set it to true, it keeps defaulting back.
When we actually managed to have it on and try to expand a PVC, we got this error:
Ignoring the PVC: didn't find a plugin capable of expanding the volume; waiting for an external controller to process this PVC.
We are using OpenShift 4.5 on bare metal CoreOS and FC for the protocol to the pmax. Creating/adding PVCs works fine.
No Events found!
a malcontent
7 Posts
0
September 17th, 2020 05:00
Answers below. We are going to tear everything down, update the operator, and redeploy/install the driver. We were using an older version of the operator. Thanks for the help. I will report back.
How did you install the driver? Did you pull the new dell-csi-operator from the github repo and installed the driver using the v1.1.0 of the Operator?
-Per my openshift admins, they used the operator in the hub. They are going to tear everything down and use a different operator, but we are operator is using image: 'dellemc/csi-powermax:v1.4.0.000R'. They are thinking the newer operator probably passes other parameters that we are missing.
Can you verify how many containers are part of your controller pod? If the installation is correct, you should see the resizer container as one of the sidecars.
-They did not tell me the total count, but we do not have a resizer sidecar.
Can you check the output of the kubectl/oc get sc command and check if your storage classes has the AllowVolumeExpansion attribute set? You should see an output like this (see text in bold)
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
powermax-test csi-powermax.dellemc.com Delete Immediate true 16h