Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2048529

Summary: yum update command failing on RHEL instance
Product: Red Hat Enterprise Linux 7 Reporter: yash
Component: rh-amazon-rhui-clientAssignee: Todd Sanders <tsanders>
Status: CLOSED WONTFIX QA Contact: Vitaly Kuznetsov <vkuznets>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.6CC: james.antill, jgreguske
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-31 07:28:12 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:

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.