proxmox-csi-plugin: CSI won't handle resize of pvc
Bug Report
Trying to resize a pvc, but csi won’t handle:
Name: some-postgres-1
Namespace: app-some
StorageClass: proxmox-data-xfs
Status: Bound
Volume: pvc-811e63d1-45e3-4987-a14c-72f359960887
Labels: cnpg.io/cluster=some-postgres
cnpg.io/instanceName=some-postgres-1
cnpg.io/instanceRole=primary
cnpg.io/pvcRole=PG_DATA
role=primary
Annotations: cnpg.io/nodeSerial: 1
cnpg.io/operatorVersion: 1.26.0
cnpg.io/pvcStatus: ready
pv.kubernetes.io/bind-completed: yes
pv.kubernetes.io/bound-by-controller: yes
volume.beta.kubernetes.io/storage-provisioner: csi.proxmox.sinextra.dev
volume.kubernetes.io/selected-node: talos-production
volume.kubernetes.io/storage-provisioner: csi.proxmox.sinextra.dev
Finalizers: [kubernetes.io/pvc-protection]
Capacity: 16Gi
Access Modes: RWO
VolumeMode: Filesystem
Used By: some-postgres-1
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning ExternalExpanding 59m volume_expand waiting for an external controller to expand this PVC
Description
The volume won’t resize …
Logs
I can see the volume in the logs in a line sarting with:
csi-provisioner I0529 17:05:46.698610 1 controller.go:1171] "handleProtectionFinalizer"
No other mentions of that pvc … and no resize
Environment
- Plugin version:
- Kubernetes version:
Client Version: v1.32.3
Kustomize Version: v5.5.0
Server Version: v1.32.3
- CSI capasity:
proxmox-data-xfs 41267203408 map[topology.kubernetes.io/region:pve topology.kubernetes.io/zone:pve]
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave “+1” or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
About this issue
- Original URL
- State: open
- Created a year ago
- Comments: 15 (14 by maintainers)
With
proxmox-csi-controller:v0.12.1andcsi-resizer:v1.13.2- as installed by version0.3.10of the chart - it seems to work now.Can confirm. Going through my helm releases and downgrading 1 by 1 fixed it, once i made it to 0.2.14, which is version v0.8.2 of the controller.
Will try to upgrade and collect logs later.