*** Bug 1777666 has been marked as a duplicate of this bug. ***
To be noted that for RBD PVC, the condition will be "FileSystemResizePending" if the PVC is not already attached to a node while doing volume expansion. Filesystem resize will succeeded and new size will be reflected once the volume is mounted. Can this be added as a note ?
Created attachment 1703066 [details] Screenshot showing FileSystemResizePending
(In reply to Jilju Joy from comment #9) > > To be noted that for RBD PVC, the condition will be > "FileSystemResizePending" if the PVC is not already attached to a node while Hi Erin, "...not already attached to a pod..." will be more appropriate instead of "...not already attached to a node...". Apologies for the mistake in previous comment. > doing volume expansion. Filesystem resize will succeeded and new size will > be reflected once the volume is mounted. > Can this be added as a note ?
Verified the content in preview: https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.5/html-single/managing_openshift_container_storage/index?lb_target=preview#scaling-persistent-volumes_rhocs
We would need to add a Note that PVC resize will be allowed only on Freshly installed clusters. The content needs to be decided based on recent discussion on PV resize in Status check meeting. Adding Needinfo on Bipin, Elad and Eran
Hi Erin, Today after discussing with stakeholders here [1] , we think we should have these changes in docs 1. remove the Warning message completely from Section 5.2 2. Rename the sub-section 5.4 as Expanding Persistent Volume Claims 3. If any doc is linking to section 5.4, need changes there as well.. e..g release note, Planning guide, managing itslf, etc 4. Change Note in 5.4 to this : This Technology Preview feature is only available with the new OpenShift Container Storage v4.5 cluster deployments. --> rephrase if there is any issue 5. Replace "Scaling Persistent Volumes" with "Expanding Persistent Volume Claims" in all places of management guide
Excellent team work in suggesting and more importantly making the changes (thanks Erin!!!). Moving to verified. Verified that all requested changes in Comment#24 and Comment#26(some were overlapping and we went with Comment#26 for re-phrasing the sentences) are made Managing guide section 5 https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.5/html-single/managing_openshift_container_storage/index?lb_target=preview#expanding-persistent-volume-claims_rhocs Some important changes done via offline chat conversations and this bug update (as updated in comment#27) =================================================================================== >Following NOTEs were rephrased to increase readability NOTE This Technology Preview feature is only available with fresh installations of OpenShift Container Storage version 4.5. It does not apply to clusters upgraded from previous OpenShift Container Storage releases. NOTE When expanding PVCs based on Ceph RADOS Block Devices (RBDs), if the PVC is not already attached to a pod the Condition type is FileSystemResizePending in the PVC’s details page. Once the volume is mounted, Filesystem resize succeeds and the new size is reflected in the Capacity field. -------------- >This was completely removed AWS restricts the number of attached interfaces, which reduces the number of storage volumes available to every server. Enabling Persistent Volume expansion to increase capacity alleviates this restriction. >RWX was removed from this statement PVC with ReadWriteOnce (RWO) access that is based on Ceph RADOS Block Devices (RBDs) with volume mode Block. ___________________________________________________________ > >> Release Notes -https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.5/html-single/4.5_release_notes/index?lb_target=preview#technology_previews Expanding Persistent Volume Claims OpenShift Container Storage 4.5 introduces the ability to expand Persistent Volume Claims as a Technology Preview feature providing more flexibility in the management of persistent storage resources. For more information, see Expanding Persistent Volume Claims