Bug 1404022

Summary: In RHV:Storage screen you can enter the same storage name for all mounts.
Product: Red Hat Quickstart Cloud Installer Reporter: James Olin Oden <joden>
Component: WebUIAssignee: cchase
Status: CLOSED ERRATA QA Contact: James Olin Oden <joden>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.1CC: cchase, dymurray, qci-bugzillas
Target Milestone: ---Keywords: Triaged
Target Release: 1.1   
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-02-28 01:42:13 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:

Description James Olin Oden 2016-12-12 21:08:40 UTC
Description of problem:
I entered in "bob" for the storage name for all the mounts, and when I hit next it worked.   I didn't go through with the deployment because I figured it would fail.    

Version-Release number of selected component (if applicable):
QCI-1.1-RHEL-7-20161209.t.0

How reproducible:
Always

Steps to Reproduce:
1.  Create a RHV(self hosted) + CFME deployment and when you get to the 
    storage screen set the storage name to the same value for all mounts.

Actual results:
It let you do this and even click next.

Expected results:
It should tell you the storage name should be unique.

Comment 2 cchase 2016-12-21 20:42:01 UTC
https://github.com/fusor/fusor/pull/1316

Enforced unique storage names (rhv, export, self-hosted)
Enforced unique host/path combinations for shares (rhv, export, self-hosted, openshift)

Comment 3 Dylan Murray 2017-01-09 13:46:21 UTC
This fix made it into the 1/6/17 compose.

Comment 4 James Olin Oden 2017-01-09 15:56:20 UTC
Compose: QCI-1.1-RHEL-7-20170106.t.0

Comment 7 errata-xmlrpc 2017-02-28 01:42:13 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, 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/RHEA-2017:0335