The PV may be in a Terminating state and cannot be deleted when the pod are created and then the pod and pvc are quickly force deleted . about kubernetes

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[tamilselvan1102]

/sig storage

[tamilselvan1102]

I think it is expected behavior. PV is not belong to any pod as long as it is bound to PVC

[dsxing]

I think it is expected behavior. PV is not belong to any pod as long as it is bound to PVC

as the bound pv's persistentVolumeReclaimPolicy is Delete, When the PVC is deleted, the PV should be deleted successfully;

In my test, Most of the time, the PV can be deleted successfully, but occasionally the PV may remain in a terminating state and cannot be deleted.

[dsxing]

ping @gnufied @jsafrane @jingxu97 Could you please take a look at this issue