-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
restoration of a volume snapshot to create a new PVC is stuck in a Pending state. #2883
Comments
vsphere-csi-controller-7b84fbfb87-9ss2d logs shows: I0509 14:38:29.794744 1 event.go:364] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"devops", Name:"postgres-storage-postgres-0-restore", UID:"0f6ab8bf-2901-41d1-b751-15a82c3b4de7", APIVersion:"v1", ResourceVersion:"59346673", FieldPath:""}): type: 'Normal' reason: 'Provisioning' External provisioner is provisioning volume for claim "devops/postgres-storage-postgres-0-restore" error: container 35b01641-4e54-44d9-b297-3fb83102a02b is not valid for pod vsphere-csi-controller-7b84fbfb87-9ss2d |
What Kubernetes distro is this? Regarding `use the snapshot create a new PVC, and created a new pod with this new PVC.', can you show the yaml of the pod and PVC? Do you mean it is a standalone pod with one Pod and one PVC? Can you show details of the StorageClass? Can you provide full logs, including vSphere CSI controller, vSphere CSI Syncer, csi-provisioner, csi-attacher? Since it says |
Xing-Yang, I have fixed the problem by delete all the pods, pvc, volumesnapshot etc. start all over. Thanks a lot for your response. |
problem fixed. |
Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT
/kind bug
/kind feature
What happened: User
I'm trying to deploy a postgresql with 3 replica and use one of its persistent volumes to do a snapshot, and use the snapshot create a new PVC, and created a new pod with this new PVC. The new PVC shows as pending.
Events:
Type Reason Age From Message
Normal Provisioning 2m39s (x307 over 18h) csi.vsphere.vmware.com_vsphere-csi-controller-7b84fbfb87-9ss2d_88c7ed5f-e04c-4489-acf8-0a58fea7026a External provisioner is provisioning volume for claim "devops/postgres-storage-postgres-0-restore"
Normal ExternalProvisioning 114s (x4483 over 18h) persistentvolume-controller Waiting for a volume to be created either by the external provisioner 'csi.vsphere.vmware.com' or manually by the system administrator. If volume creation is delayed, please verify that the provisioner is running and correctly registered.
Reference: https://docs.vmware.com/en/VMware-vSphere-Container-Storage-Plug-in/3.0/vmware-vsphere-csp-getting-started/GUID-E0B41C69-7EEB-450F-A73D-5FD2FF39E891.html
What you expected to happen:
After I restore the volume snapshot to a new PVC, It should show as Bound.
How to reproduce it (as minimally and precisely as possible):
Even I deleted the PVC which was created from the volume snapshot, deleted the vsphere-csi-controller and vsphere-csi-node; make sure new csi controller and nodes are recreated; recreate the pvc with volume snapshot, still shows Pending.
Anything else we need to know?:
Environment:
uname -a
): Linux xxx 5.15.0-97-generic Support for Metrics #107-Ubuntu SMP Wed Feb 7 13:26:48 UTC 2024 x86_64 x86_64 x86_64 GNU/LinuxThe text was updated successfully, but these errors were encountered: