Bug 1323742

Summary: 'CDS' notation is not used in CDS menu
Product: Red Hat Update Infrastructure for Cloud Providers Reporter: Irina Gulina <igulina>
Component: ToolsAssignee: Patrick Creech <pcreech>
Status: CLOSED ERRATA QA Contact: Radek Bíba <rbiba>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.0.0CC: pcreech
Target Milestone: ---Keywords: EasyFix
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-01 22:11:49 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 Irina Gulina 2016-04-04 15:06:36 UTC
Description of problem:

In menu 'Content Delivery Server' is notated as 'CDS', but this notation is not used further in description of l, a, r, d options. 

RHUI3
 
 
------------------------------------------------------------------------------
             -= Red Hat Update Infrastructure Management Tool =-
 
 
-= Content Delivery Server (CDS) Management =-
 
   l   list all known Content Delivery Server instances managed by the RHUI
   a   register (add) a new Content Delivery Server instance
   r   reinstall and reapply configuration to an existing Content Delivery Server instance
   d   unregister (delete) a Content Delivery Server instance from the RHUI
 
                                                   Connected: rhua.example.com
------------------------------------------------------------------------------
rhui (cds) =>
 
 
However 'CDS' notation was used in RHUI2. I think it looks better and more readable with 'CDS'.
 
------------------------------------------------------------------------------
             -= Red Hat Update Infrastructure Management Tool =-
 
 
-= Content Delivery Server (CDS) Management =-
 
   l   list all CDS clusters and instances managed by the RHUI
   i   display detailed information on a CDS cluster
   a   register (add) a new CDS instance
   m   move CDS(s) to a different cluster
   d   unregister (delete) a CDS instance from the RHUI
   s   associate a repository with a CDS cluster
   u   unassociate a repository from a CDS cluster


Version-Release number of selected component (if applicable):
>> rpm -qa "*rhui*"
rhui-installer-base-0.0.24-1.el7ui.noarch
rh-amazon-rhui-client-rhs30-2.2.124-1.el7.noarch
rhui-installer-0.0.24-1.el7ui.noarch
rh-rhui-tools-libs-pre.3.0.16-1.el7ui.noarch
rh-amazon-rhui-client-2.2.124-1.el7.noarch
rh-rhui-tools-pre.3.0.16-1.el7ui.noarch
rhui-default-ca-1.0-1.noarch

RHUI iso 20151013

How reproducible:
always

Steps to Reproduce:
1. From home screen go to CDS screen: 'c' 

Expected results:

------------------------------------------------------------------------------
             -= Red Hat Update Infrastructure Management Tool =-
 
 
-= Content Delivery Server (CDS) Management =-
 
   l   list all known CDS instances managed by the RHUI
   a   register (add) a new CDS instance
   r   reinstall and reapply configuration to an existing CDS instance
   d   unregister (delete) a CDS instance from the RHUI
 
                                                   Connected: rhua.example.com
------------------------------------------------------------------------------
rhui (cds) =>

Comment 4 Radek Bíba 2016-08-16 11:22:29 UTC
Fixed in the latest RHEL 6 and 7 ISOs:

-= Content Delivery Server (CDS) Management =-

   l   list all known CDS instances managed by the RHUI
   a   register (add) a new CDS instance
   r   reinstall and reapply configuration to an existing CDS instance
   d   unregister (delete) a CDS instance from the RHUI

Comment 5 errata-xmlrpc 2017-03-01 22:11:49 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/RHBA-2017:0367