Bug 1374085

Summary:	OpenShift Configuration page 3B: field for Gluster export path requires a leading slash.
Product:	Red Hat Quickstart Cloud Installer	Reporter:	bmorriso
Component:	WebUI	Assignee:	Dylan Murray <dymurray>
Status:	CLOSED ERRATA	QA Contact:	bmorriso
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.0	CC:	dymurray, tsanders
Target Milestone:	ga	Keywords:	Triaged
Target Release:	1.0
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:	2016-09-13 16:38:28 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 bmorriso 2016-09-07 23:00:06 UTC

Description of problem:

On OpenShift configuration page, when configuring persistent Gluster storage for the OpenShift internal Docker registry, the WebUI requires that the Gluster export path have a leading slash. This slash should not be present for a Gluster export path.

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

How reproducible:
100%

Steps to Reproduce:
1. On OpenShift Configuration page 3B, select Gluster for the OpenShift internal Docker Registry.
2. Enter the IP Address/Hostname for the Gluster Server
3. Enter the export path for the Gluster share

Actual results:
Error message appears that the Export Path requires a leading slash, unable to continue to the next page without adding it.

Expected results:
Page accepts the correct export share path and allows you to continue.

Additional info:

If you add the leading slash and continue with the deployment, the OSE deployment will succeed, but the Hello World example application will not deploy successfully.

Comment 3 Dylan Murray 2016-09-08 15:08:13 UTC

https://github.com/fusor/fusor/pull/1216

Comment 4 bmorriso 2016-09-09 16:23:25 UTC

Verified with QCI-1.0-RHEL-7-20160908.1

The export path field for Gluster no longer requires a leading slash.

Comment 6 errata-xmlrpc 2016-09-13 16:38:28 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-2016:1862