Bug 1306816

Summary: RHEV Configuration: Update string telling users to change the Cluster Name after altering the Data Center Name
Product: Red Hat Quickstart Cloud Installer Reporter: Matt Reid <mreid>
Component: WebUIAssignee: John Matthews <jmatthew>
Status: CLOSED ERRATA QA Contact: Tasos Papaioannou <tpapaioa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0CC: tpapaioa
Target Milestone: gaKeywords: Triaged
Target Release: 1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-13 16:26:21 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:
Attachments:
Description Flags
Triggered Message none

Description Matt Reid 2016-02-11 18:59:49 UTC 
Description of problem:
If you go through and try to change the Data Center Name during RHEV Configuration, apparently the Cluster Name must be updated as well. The string that is triggered when you adjust Data Center Name says: "Note: You must change the cluster name after changing the database name."

Maybe it's a database name on the backend, but that isn't what the field we just altered refers to it as. At minimum, we should update this string so that it correctly identifies both fields as seen in the GUI. 

"Note: You must change the cluster name after changing the database name."

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

How reproducible:
always


Additional info:
Comment 1 Matt Reid 2016-02-11 19:00:45 UTC 
Created attachment 1123281 [details]
Triggered Message
Comment 2 Tasos Papaioannou 2016-06-29 18:02:33 UTC 
Verified on QCI-1.2-RHEL-7-20160627.t.0.
Comment 8 errata-xmlrpc 2016-09-13 16:26:21 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