Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1408279

Summary:	Web console allows selecting EBS with RWX volumes
Product:	OpenShift Container Platform	Reporter:	Stefanie Forrester <dakini>
Component:	Storage	Assignee:	Pavel Pospisil <ppospisi>
Status:	CLOSED NOTABUG	QA Contact:	Wenqi He <wehe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.4.1	CC:	aos-bugs, bchilds, dakini, hchen, jokerman, mmccomas, sten
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-11 18:30:08 UTC	Type:	Bug
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:
Bug Blocks:	1303130

Description Stefanie Forrester 2016-12-22 17:38:39 UTC

Description of problem:

In the web console, when creating a new storage volume, the user is presented with some incompatible storage options.

In the web console, from my application page, I click: App -> Storage -> Create Storage.

From there, I'm shown that our storage class is EBS.

Storage Class: EBS

And I'm allowed to select "Shared access (RWX)" to access my EBS volume.

But in reality, EBS and similar cloud-based storage are RWO. They can only be attached in write-mode on a single instance.

It would be great if the web console could look at our storage class and remove the option for RWX when using EBS and Google Persistent Disks.


Version-Release number of selected component (if applicable):
3.4

How reproducible:
100%

Steps to Reproduce:
1. Create an example app. I used 'cakephp-mysql-persistent'.
2. On the overview page, click "Storage" and then "Create Storage".
3. 

Actual results:

User is presented with RWX even though RWX will never work with cloud-based storage.

Expected results:

User should not be allowed to request incompatible storage options.

Additional info:

Comment 3 Jessica Forrester 2017-01-03 13:58:25 UTC

assigning to the Storage team as I'm not sure there is much we can do client side, we typically do not prevent something that the API allows.