Bug 1347328

Summary:	Product Naming Inconsistencies for Red Hat OpenStack Platform
Product:	Red Hat Quickstart Cloud Installer	Reporter:	Katherine Dubé <kdube>
Component:	WebUI	Assignee:	Derek Whatley <dwhatley>
Status:	CLOSED ERRATA	QA Contact:	Thom Carlin <tcarlin>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	1.0	CC:	jkim, jmatthew, tcarlin
Target Milestone:	ga	Keywords:	Triaged
Target Release:	1.0
Hardware:	All
OS:	Linux
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:29:58 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:	1342594

Description Katherine Dubé 2016-06-16 14:03:45 UTC

Description of problem:

Red Hat's version of OpenStack has been officially named to "Red Hat OpenStack Platform", or "RHOSP" for short. There's a number of instances in the QCI WebUI where the incorrect product name is used and should be fixed.

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


How reproducible:
100%


Steps to Reproduce:
1. Normal QCI WebUI-based Deployment

Actual results:

1. Step 4A - OpenShift:
Select where to provision the OpenShift Enterprise nodes: Red Hat Enterprise Linux OpenStack Platform 

2. Step 7A - Installation Review:
RHOSP

3. Step 7C - Installation Summary:
Red Hat Enterprise Linux - OpenStack Platform

Expected results:

1. Step 4A - OpenShift
Select where to provision the OpenShift Enterprise nodes: Red Hat OpenStack Platform 

2. Step 7A - Installation Review:
Red Hat OpenStack Platform

3. Step 7C - Installation Summary:
Red Hat OpenStack Platform


Additional info:
Should be fixed for 1.0 GA release.

Comment 1 Derek Whatley 2016-06-27 17:54:09 UTC

MR created at:
https://github.com/jwmatthews/fusor/pull/1/commits/bdd77669eabc7243292c7023bebb3fa0aea68609


Additionally please note:
I changed the string generating function "fullnameOpenShift" to generate "OpenShift Enterprise" instead of "OpenShift Enterprise by Red Hat".


Names being used (for reference):

Full Names:
- Red Hat Enterprise Virtualization
- Red Hat OpenStack Platform
- Red Hat Cloud Forms Management Engine
- OpenShift Enterprise (previously "OpenShift Enterprise by Red Hat", but I figured the "by Red Hat" is completely necessary given the user knows they are inside of a Red Hat installer)

Comment 2 Derek Whatley 2016-06-27 17:55:06 UTC

Correction

>- OpenShift Enterprise (previously "OpenShift Enterprise by Red Hat", but I figured the "by Red Hat" **__isn't__** completely necessary given the user knows they are inside of a Red Hat installer)

Comment 3 Derek Whatley 2016-06-28 20:38:55 UTC

New PR created at https://github.com/fusor/fusor/pull/991
Somehow I had previously forked jmatthews' fusor fork. Fixed now.

Comment 4 John Matthews 2016-07-05 17:33:22 UTC

QCI-1.2-RHEL-7-20160705.t.1

Comment 5 Thom Carlin 2016-07-12 19:32:57 UTC

NOTE: Reproduction steps assume selections not listed so the step may differ.

* OpenShift Master/Nodes shows "Red Hat OpenStack Platform"
* Installation Review shows "Red Hat OpenStack Platform"

Comment 12 jkim 2016-09-01 20:18:31 UTC

Ready to Test!

Comment 13 Thom Carlin 2016-09-10 12:13:27 UTC

1) RHOSP -> Register Nodes displays "Loading OSP nodes"
2) RHOSP -> Register Nodes displays "Register at least 2 nodes with the selected undercloud to build out your OpenStack environment."
3) RHOSP -> Register Nodes, Register Nodes button displays "Nodes are registered with OpenStack by connecting to their power management interfaces. In some environments, nodes can be auto-detected using those interfaces"

Comment 14 Thom Carlin 2016-09-10 13:58:56 UTC

Verified in fusor-release-1.0.0-3.el7_2 by visually examining each step in RHOSP deployment process

Comment 16 errata-xmlrpc 2016-09-13 16:29:58 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