k8s-cinder integration does not clean up volumes in openstack when Persistent Volumes get deleted

Bug #2063302 reported by ashutosh gautam
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Openstack Integrator Charm
New
Undecided
Unassigned

Bug Description

The integration between Kubernetes (k8s) and Cinder does not consistently remove volumes in OpenStack when Persistent Volumes (PVs) are deleted.

This issue has been observed multiple times, where volumes created in OpenStack through PersistentVolumeClaims (PVCs) and PersistentVolumes (PVs) are not deleted from OpenStack after the corresponding PVs are deleted.

The problem seems to be intermittent, occurring unpredictably. Sometimes the volumes are cleaned up properly, while other times they persist in OpenStack despite the deletion of their corresponding PVs.

Reproduction Steps:

1. Create a PVC using the storage class with the provisioner: cinder.csi.openstack.org.
2. Delete the PV attached to the PVC.

Note: Due to the intermittent nature of the issue, reproducing it consistently may be challenging on an ideal scenario. But the above steps are kind of similar to what we are facing.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.