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.
[root@ip-10-80-66-31 ~]# yum update rh-amazon-rhui-client
Loaded plugins: amazon-id, priorities, rhui-lb, security
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package rh-amazon-rhui-client.noarch 0:2.2.85-1.el6_4 will be updated
---> Package rh-amazon-rhui-client.noarch 0:2.2.92-1.el6_4 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
=====================================================================================================================
Package Arch Version Repository Size
=====================================================================================================================
Updating:
rh-amazon-rhui-client noarch 2.2.92-1.el6_4 rhui-REGION-client-config-server-6 46 k
Transaction Summary
=====================================================================================================================
Upgrade 1 Package(s)
Total size: 46 k
Is this ok [y/N]: y
Downloading Packages:
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID f21541eb: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-auxiliary
GPG key retrieval failed: [Errno 14] Could not open/read file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-auxiliary
[root@ip-10-80-66-31 ~]# cat /etc/yum.repos.d/redhat-rhui-client-config.repo
# The amazon ec2 region is now dynamically set via yum. REGION can be replaced by the amazon ec2 region for debugging
[rhui-REGION-client-config-server-6]
name=Red Hat Update Infrastructure 2.0 Client Configuration Server 6
mirrorlist=https://rhui2-cds01.REGION.aws.ce.redhat.com/pulp/mirror/rhui-client-config/rhel/server/6/$basearch/os
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-auxiliary
sslverify=1
sslcacert=/etc/pki/entitlement/cdn.redhat.com-chain.crt
sslclientcert=/etc/pki/entitlement/product/rhui-client-config-server-6.crt
sslclientkey=/etc/pki/entitlement/rhui-client-config-server-6.key
[root@ip-10-80-66-31 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.4 (Santiago)
How reproducible:
Always
cloude commit: ec2-184-169-229-135.us-west-1.compute.amazonaws.com
Fix can be found in rh-amazon-rhui-client-2.2.93-1.
Comment 4RHEL Program Management
2013-10-13 23:03:55 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.