PV with reclam policy can never be claimed again in vclusters

[jpuyobro]

What happened?

With a Vcluster (with persistentVolumes enabled, nodes sync enabled, hoststorageClasses enabled, A volume created with Reclaim policy can never be reclaim. The PV never return to "Available" state.

What did you expect to happen?

We should be able to reclaim this PV inside a vcluster and attach it again.

How can we reproduce it (as minimally and precisely as possible)?

How to reproduce :

1. In a vCluster Create a PVC with reclaim policy set to retain, a PV is created
2. Remove the pods using it
3. Delete the PVC: the PV go to state "Released"
4. Edit the PV to remove in the spec the "claimRef" part
   In a non-vcluster env, the PV goes to state "Available" and can be claimed again
   In a vcluster env, the PV stays in the state "Released" and a claimRef is added (it can't be removed). The claim ref is the claim information on "host" cluster

Anything else we need to know?

No response

Host cluster Kubernetes version

$ kubectl version
v1.28.0

Host cluster Kubernetes distribution

# Write here

vlcuster version

$ vcluster --version
0.18.1

Vcluster Kubernetes distribution(k3s(default)), k8s, k0s)

v1.28.2+k3s1

OS and Arch

OS: Talos
Arch:

[jpuyobro]

Hey guys, Any news on that one ?

[ThomasK33]

Hey @jpuyobro, thanks for opening the issue. I'll look into reproducing this behavior.

[jpuyobro]

Hey guys, any news on this issue ?

[facchettos]

Hi, sorry for the delayed answer, I have been able to reproduce it on our latest version, I am looking into it