Bug 2072573 - [4.8] local pv's are in terminating state
Summary: [4.8] local pv's are in terminating state
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.9
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 4.8.z
Assignee: Jonathan Dobson
QA Contact: Penghao Wang
Lisa Pettyjohn
URL:
Whiteboard:
Depends On: 2070617
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-06 14:44 UTC by OpenShift BugZilla Robot
Modified: 2022-04-20 12:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Release Note
Doc Text:
In prior releases, the Local Storage Operator added an OwnerReference to the Persistent Volumes it created such that deletion of the node would also issue a delete request for the PV. This caused an issue in some situations where the PV could be left in the "Terminating" state while still attached to a pod. LSO no longer creates that OwnerReference, which means cluster administrators will need to delete any unused PV's after a node is removed from the cluster. Please see the documentation on "Persistent storage using local volumes" for more details.
Clone Of:
Environment:
Last Closed: 2022-04-20 12:22:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift local-storage-operator pull 342 0 None open [release-4.8] Bug 2072573: local pv's are in terminating state 2022-04-06 14:51:34 UTC
Red Hat Product Errata RHBA-2022:1369 0 None None None 2022-04-20 12:22:32 UTC

Comment 7 errata-xmlrpc 2022-04-20 12:22:15 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.37 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-2022:1369
Note You need to log in before you can comment on or make changes to this bug.