Repository: kubernetes
Issue: PVC goes into Lost state
Labels: kind/bug,sig/storage,lifecycle/stale,triage/needs-information,needs-triage

### What happened?

Deploying a host path PVC results in Lost state.

1. User deployes below Persistent Volume.

```
kubectl get pv host-only-pv -oyaml

apiVersion: v1
kind: PersistentVolume
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"PersistentVolume","metadata":{"annotations":{},"name":"host-only-pv"},"spec":{"accessModes":["ReadWriteOnce"],"capacity":{"storage":"1Gi"},"hostPath":{"path":"/mnt/tmp-host","type":"DirectoryOrCreate"},"persistentVolumeReclaimPolicy":"Retain"}}
    pv.kubernetes.io/bound-by-controller: "yes"
  creationTimestamp: "2024-09-10T07:33:09Z"
  finalizers:
  - kubernetes.io/pv-protection
  name: host-only-pv
  resourceVersion: "353506815"
  uid: 47ac2af2-ecd2-4ccd-8ee0-93b872980640
spec:
  accessModes:
  - ReadWriteOnce
  capacity:
    storage: 1Gi
  claimRef:
    apiVersion: v1
    kind: PersistentVolumeClaim
    name: host-only-pvc
    namespace: bkp-pvc
    resourceVersion: "353506793"
    uid: be600292-2d9e-46db-b0f3-df709741930b
  hostPath:
    path: /mnt/tmp-host
    type: DirectoryOrCreate
  persistentVolumeReclaimPolicy: Retain
  volumeMode: Filesystem
status:
  phase: Bound
```
2. User creates Persistent volume claim reffering to Persiste volume created in step 1 but this PVC immidately moves into `Lost` Status.

```
kubectl get pvc host-only-pvc -n bkp-pvc -oyaml

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"PersistentVolumeClaim","metadata":{"annotations":{},"name":"host-only-pvc","namespace":"bkp-pvc"},"spec":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}}}}
    pv.kubernetes.io/bind-completed: "yes"
    pv.kubernetes.io/bound-by-controller: "yes"
  creationTimestamp: "2024-09-10T07:33:09Z"
  finalizers:
  - kubernetes.io/pvc-protection
  name: host-only-pvc
  namespace: bkp-pvc
  resourceVersion: "353508452"
  uid: be600292-2d9e-46db-b0f3-df709741930b
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi
  volumeMode: Filesystem
  volumeName: host-only-pv
status:
  phase: Lost
```

### What did you expect to happen?

PVC should remain in bound state.

### How can we reproduce it (as minimally and precisely as possible)?

-

### Anything else we need to know?

I have attached kube-controller-managerlog here, where bunch of `Bound claim has lost its PersistentVolume. Data on the volume is lost!` error messages can be seen happening for other volumes as well.

[kube-controller-managerlogs.txt](https://github.com/user-attachments/files/16944022/kube-controller-managerlogs.txt)


### Kubernetes version

<details>

```console
$ kubectl version
# 1.27.0
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ uname -a
# Linux ISVBK8CL3T06 4.18.0-553.5.1.el8_10.x86_64 #1 SMP Tue May 21 03:13:04 EDT 2024 x86_64 x86_64 x86_64 GNU/Linux

```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>
CRI-O
</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>