Bug 2008088
| Summary: | [4.8.z] PVs remain in Released state for a long time after the claim is deleted | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Tomas Smetana <tsmetana> |
| Component: | Storage | Assignee: | Hemant Kumar <hekumar> |
| Storage sub component: | Local Storage Operator | QA Contact: | Rohit Patil <ropatil> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | urgent | ||
| Priority: | urgent | CC: | alosadag, aos-bugs, aos-storage-staff, bzhai, cback, chaoyang, colleen.o.malley, djuran, hekumar, jsafrane, mavazque, mblach, pibanezr, wduan, wking |
| Version: | 4.8 | Keywords: | FastFix |
| Target Milestone: | --- | ||
| Target Release: | 4.8.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | Telco | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
Local Storage Operator deleted orphaned PersistentVolumes (PVs) with 10 second delay and the delay was cumulative. With many PersistentVolumeClaims (PVCs) deleted at the same time, it could took minutes and hours to get their PVs deleted.
Consequence:
PVs were not deleted and corresponding local disks were not available for new PVCs for hours.
Fix:
The 10 second delay was removed.
Result:
PVs are deleted and corresponding local disks are made available for new PVCs much more quickly.
|
Story Points: | --- |
| Clone Of: | 2007684 | Environment: | |
| Last Closed: | 2021-10-19 20:35:31 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: | 2007684 | ||
| Bug Blocks: | |||
|
Comment 5
Jan Safranek
2021-10-15 13:55:25 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.8.15 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:3821 |