Bug 1971231 - [4.7][Local storage] PV provisioned by localvolumeset stays in "Released" status after the pod/pvc deleted
Summary: [4.7][Local storage] PV provisioned by localvolumeset stays in "Released" sta...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.7
Hardware: Unspecified
OS: Unspecified
low
high
Target Milestone: ---
: 4.7.z
Assignee: Fabio Bertinatto
QA Contact: Chao Yang
URL:
Whiteboard:
Depends On: 1937145 1952820
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-13 05:32 UTC by Wei Duan
Modified: 2022-08-19 12:19 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: PV events weren't correctly triggering a reconcile Consequence: Released PVs weren't being properly cleaned up Fix: Correctly trigger a reconcile based on PV events Result: Released PVs are being properly cleaned up
Clone Of: 1937145
Environment:
Last Closed: 2022-08-19 12:19:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Jan Safranek 2021-06-15 14:51:03 UTC 
@wduan, the fix in 4.8 is huge and may introduce regressions. Do we really want this fixed in 4.7? So far, we did not see any customers hitting this issue and we have documented that manual PV cleanup is needed.
Comment 2 Wei Duan 2021-06-16 07:02:49 UTC 
As this is the last step(user want to delete the pvc/pv) and we have the documented the manual step, I agree to close it if we have risk to fix it.
Comment 3 Jan Safranek 2021-06-18 14:01:14 UTC 
Thanks for your response. Closing for now, we may reconsider if there is a strong customer request.
Comment 4 Hemant Kumar 2021-06-18 14:16:24 UTC 
I reopened this BZ, because ideally speaking if a PVC is deleted then corresponding PV should become Available. It should be consistent with how LocalVolume objects behave and manual cleanup steps don't cover deletion of PVCs, they are for deletion of LocalVolume or LocalVolumeSet objects.
Comment 5 Rohan CJ 2021-06-21 04:37:02 UTC 
I'll make a direct fix for 4.7 that doesn't depend on the large changes for 4.8. It's probably a watching issue.
Note You need to log in before you can comment on or make changes to this bug.