Bug 1348280 - [RFE] change *rhui2* name of CDS load balancer to *rhui3*
Summary: [RFE] change *rhui2* name of CDS load balancer to *rhui3*
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Update Infrastructure for Cloud Providers
Classification: Red Hat
Component: Operations
Version: 3.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: dgao
QA Contact: Vratislav Hutsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-20 16:32 UTC by Irina Gulina
Modified: 2018-04-10 07:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-23 18:28:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Irina Gulina 2016-06-20 16:32:04 UTC 
Description of problem:

Operating on RHUI3, it's confusing to see *rhui2* in CDS load balancers' names. 

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

How reproducible:
always

Actual results: 
>> yum info pulp-selinux
Loaded plugins: amazon-id, rhui-lb, search-disabled-repos
Could not contact CDS load balancer rhui2-cds01.eu-west-1.aws.ce.redhat.com, trying others.


Could not contact any CDS load balancers: rhui2-cds01.eu-west-1.aws.ce.redhat.com, rhui2-cds02.eu-west-1.aws.ce.redhat.com.

Expected results:
rhui3-cds01.eu-west-1.aws.ce.redhat.com,
rhui3-cds02.eu-west-1.aws.ce.redhat.com
Comment 3 bizhang 2016-10-24 14:23:43 UTC 
This looks to be specific to the amazon provisioning scripts and not a RHUI3 issue.

Please verify that this issue is resolved when the hostname of the CDS load balancers are changed to rhui3-cds* and reregistered with RHUI
Comment 6 dgao 2016-11-23 18:28:06 UTC 
This issue stems from using a version of rhui-client that's meant to access content from RHUI2. The proper solution to this is to create a new (fork) rhui-client that is targeted to access content from RHUI3. Closing w/ NEXTRELEASE flag.
Note You need to log in before you can comment on or make changes to this bug.