Bug 2048529 - yum update command failing on RHEL instance
Summary: yum update command failing on RHEL instance
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rh-amazon-rhui-client
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Todd Sanders
QA Contact: Vitaly Kuznetsov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-31 12:47 UTC by yash
Modified: 2023-07-31 07:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-31 07:28:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-110398 0 None None None 2022-01-31 12:47:52 UTC

Description yash 2022-01-31 12:47:00 UTC
Description of problem:
On running the yum update command on the RHEL instance I am seeing an issue which is as follows:

[root@ip-10-0-0-242 ~]# yum update -y
Loaded plugins: amazon-id, rhui-lb, search-disabled-repos
Could not contact any CDS load balancers: https://rhui3.us-east-1.aws.ce.redhat.com/pulp/content/.

Not sure of the exact cause of the problem but I see no similar issue reported in the recent past for RHEL. I have created this instance on AWS with AMI Id:ami-011b3ccf1bd6db744.

Version-Release number of selected component (if applicable):
"Red Hat Enterprise Linux Server 7.6 (Maipo)"

How reproducible:
yum update -y

Steps to Reproduce:
1.yum update -y

Actual results:
Could not contact any CDS load balancers: https://rhui3.us-east-1.aws.ce.redhat.com/pulp/content/.

Expected results:
No error

Comment 3 Jaroslav Mracek 2022-02-08 10:44:12 UTC
I tried to investigate the issue and I searched for the string `Could not contact any CDS load balancers:` and it looks like that there are multiple hints with it. I suggest that `Could not contact any CDS load balancers:` is related to amazon-id or rhui-lb plugin but I cannot prove it.

Basically the issue looks like an infrastructure issue when some parts of infrastructure are not accessible. I am changing the component but I am not 100% sure whether I picked the correct one.

Comment 5 RHEL Program Management 2023-07-31 07:28:12 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.