Bug 1939021 - RBD RWX PVC creation with Filesystem volume mode selection is creating RWX PVC with Block volume mode instead of disabling Filesystem volume mode selection
Summary: RBD RWX PVC creation with Filesystem volume mode selection is creating RWX P...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.7.z
Assignee: gowtham
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On: 1936788
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-15 13:17 UTC by gowtham
Modified: 2021-06-09 06:20 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1936788
Environment:
Last Closed: 2021-06-09 06:19:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description gowtham 2021-03-15 13:17:37 UTC 
+++ This bug was initially created as a clone of Bug #1936788 +++

Description of problem:

If Ceph RBD storage class and RWX access mode is selected, the option to select Volume mode is still enabled. So Filesystem volume mode can be selected for RDB RWX PVC which is not supported. Clicking on create button will not throw any error but the volume mode of the created PVC will be Block.


Version-Release number of selected component (if applicable):
4.7.0-0.nightly-2021-03-06-183610

How reproducible:
Always

Steps to Reproduce:
1. Go to Storage --> PersistentVolumeClaims and click on "Create PersistentVolumeClaim" button.
2. Select project 
3. Select RBD Storage Class and fill Persistent Volume Claim Name.
4. Select Access Mode "Shared Access (RWX)".
5. Give the required PVC Size.
6. Select Volume Mode "Filesystem"
7. Click on "Create" button


Actual results:
PVC will be created with volume mode as Block.


Expected results:
Selection of Volume Mode "Filesystem" should be disabled if RBD storage class and RWX Access Mode is selected. 

Additional info:
Note You need to log in before you can comment on or make changes to this bug.