not registered as CNS Volume

[pbs-jyu]

Is this a BUG REPORT:

Uncomment only one, leave it on its own line:

/kind bug

What happened: Kubectl get pv and pvc shows expected; within vcenter only some of the volumes. After I have created pvc initially, I did see all of them in vcenter. Not sure when it disappeared. though the PVC attached seems functioning without problem.

kg pv -A NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS VOLUMEATTRIBUTESCLASS REASON AGE pvc-1d849509-eed8-48ca-8e07-8d151a5c45c9 30Gi RWO Retain Bound devops/prm-esxi-eksa-1-microk8s-01-restored prm-esxi-eksa-1-microk8s-sc 4d23h pvc-46468f57-4aab-4ff3-b8ff-d68d556fb8d3 10Gi RWO Retain Bound devops/prm-esxi-eksa-1-microk8s01-testpod1-pvc prm-esxi-eksa-1-microk8s-sc 25h pvc-817d78cc-f490-4dfb-857a-415e283f4d70 30Gi RWO Retain Bound devops/postgres-storage-postgres-0 prm-esxi-eksa-1-microk8s-sc 4d23h

kg pvc -A NAMESPACE NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS VOLUMEATTRIBUTESCLASS AGE devops postgres-storage-postgres-0 Bound pvc-817d78cc-f490-4dfb-857a-415e283f4d70 30Gi RWO prm-esxi-eksa-1-microk8s-sc 4d23h devops prm-esxi-eksa-1-microk8s-01-restored Bound pvc-1d849509-eed8-48ca-8e07-8d151a5c45c9 30Gi RWO prm-esxi-eksa-1-microk8s-sc 4d23h devops prm-esxi-eksa-1-microk8s01-testpod1-pvc Bound pvc-46468f57-4aab-4ff3-b8ff-d68d556fb8d3 10Gi RWO prm-esxi-eksa-1-microk8s-sc 25h

within vcenter, I only see the following two volumes: pvc-1d849509-eed8-48ca-8e07-8d151a5c45c9
pvc-46468f57-4aab-4ff3-b8ff-d68d556fb8d3
later, when I refresh in vcenter, I won't see any volume. rescaning the storage won't make any difference.

What you expected to happen: I should see all 3 Volumes;

How to reproduce it (as minimally and precisely as possible): not sure how to reproduce this.

Anything else we need to know?:

Environment:

• csi-vsphere version: 3.3.0

• vsphere-cloud-controller-manager version: 1.30

• Kubernetes version: 1.29

• vSphere version: 8.0.2.00300

• OS (e.g. from /etc/os-release):

• PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=jammy

• Kernel (e.g. uname -a): Linux s-mick8s1-dt1-x 6.5.0-41-generic #41~22.04.2-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun 3 11:32:55 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

• Install tools: Microk8s cluster. - Others:

[Midaxess]

I have the same issue with more or less the same environnent as you

I don't know why but after a radom time, pods are able to link their volumes

If you find a solution, I'm interested

[aditya-tanwar]

Hi , were you able to find a solution for this ?

[JanikMie]

Are there any news? I think we have the same problem.

[Midaxess]

Personnaly, it was due to a wrong config between 2 clusters with vsphere-csi :

I had the same cluster-id in the vsphere-config-secret of 2 clusters k8s I followed this article to fix it and now in the File Share section of my vCenter, I no longer see volumes randomly appearing and disappearing.