Bug 1971231
| Summary: | [4.7][Local storage] PV provisioned by localvolumeset stays in "Released" status after the pod/pvc deleted | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Wei Duan <wduan> |
| Component: | Storage | Assignee: | Fabio Bertinatto <fbertina> |
| Storage sub component: | Local Storage Operator | QA Contact: | Chao Yang <chaoyang> |
| Status: | CLOSED WONTFIX | Docs Contact: | |
| Severity: | high | ||
| Priority: | low | CC: | chaoyang, hekumar, jsafrane, rkant, ropatil |
| Version: | 4.7 | Keywords: | Regression, Reopened |
| Target Milestone: | --- | ||
| Target Release: | 4.7.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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
|
Story Points: | --- |
| Clone Of: | 1937145 | Environment: | |
| Last Closed: | 2022-08-19 12:19:37 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1937145, 1952820 | ||
| Bug Blocks: | |||
|
Comment 1
Jan Safranek
2021-06-15 14:51:03 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. Thanks for your response. Closing for now, we may reconsider if there is a strong customer request. 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. 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. |