As mentioned in the title, I found that PVCs cannot be expanded directly with HPE CSI Driver when volumes are created using the Remote Copy。We had HPE CSI Driver 2.2.0 installed in Kubernetes 1.21. Our storages are 2 Alletra-9060 arrays configed Remote Copy in 2DC Peer Persistence mode. When using “kubectl patch or edit” command to expand pvc, there are errors reported as follows from volume_expand and externel-resizer csi.hpe.com.
"lgnoring the PVC: didn't find a plugin capable of expanding the volume; waiting for an extern
al controller to process this PVC."
"resize volume "pvc-6eeedcac-4b0c-4ec9-9848-1d6fbe498eeb"by resizer "csi.hpe.com"faile d: rpc error: code = Internal desc= Failed to expand volume to requested size, Request faile d with status code 400 and errors Error code (Bad Request) and message (HTTP error respo nse from backend {"code":29,"desc":"Error: Cannot grow local volume\n VV pvc-6eeedcac-4b0c-4ec9-9848-1d6 is currently in a started remote copy group. The group must be stopped b efore the volume's user space can be grown."])"
Accoding to these errors, I need to stop the rocopy group first, then I can extend pvc successfully and I need to start the rcopygroup manually, which is really inconvenient.
So, will HPE realizes some functions to solve Peer Persistence Volume expansion problem in the furture? Do we have some method to expand PP PVC gracefully？
After all, not all customers can use the storage command line to finish these tasks.
As mentioned in the title, I found that PVCs cannot be expanded directly with HPE CSI Driver when volumes are created using the Remote Copy。We had HPE CSI Driver 2.2.0 installed in Kubernetes 1.21. Our storages are 2 Alletra-9060 arrays configed Remote Copy in 2DC Peer Persistence mode. When using “kubectl patch or edit” command to expand pvc, there are errors reported as follows from volume_expand and externel-resizer csi.hpe.com. "lgnoring the PVC: didn't find a plugin capable of expanding the volume; waiting for an extern al controller to process this PVC." "resize volume "pvc-6eeedcac-4b0c-4ec9-9848-1d6fbe498eeb"by resizer "csi.hpe.com"faile d: rpc error: code = Internal desc= Failed to expand volume to requested size, Request faile d with status code 400 and errors Error code (Bad Request) and message (HTTP error respo nse from backend {"code":29,"desc":"Error: Cannot grow local volume\n VV pvc-6eeedcac-4b0c-4ec9-9848-1d6 is currently in a started remote copy group. The group must be stopped b efore the volume's user space can be grown."])" Accoding to these errors, I need to stop the rocopy group first, then I can extend pvc successfully and I need to start the rcopygroup manually, which is really inconvenient. So, will HPE realizes some functions to solve Peer Persistence Volume expansion problem in the furture? Do we have some method to expand PP PVC gracefully？ After all, not all customers can use the storage command line to finish these tasks.