Bug 1408279 - Web console allows selecting EBS with RWX volumes
Summary: Web console allows selecting EBS with RWX volumes
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.4.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Pavel Pospisil
QA Contact: Wenqi He
URL:
Whiteboard:
Depends On:
Blocks: OSOPS_V3
TreeView+ depends on / blocked
 
Reported: 2016-12-22 17:38 UTC by Stefanie Forrester
Modified: 2017-05-11 18:30 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-11 18:30:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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