Hide Forgot
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.
https://github.com/fusor/fusor/pull/1216
Verified with QCI-1.0-RHEL-7-20160908.1 The export path field for Gluster no longer requires a leading slash.
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