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.
One of the configured repositories failed (Red Hat Enterprise Linux 7 Server - Extended Update Support (RPMs)), and yum doesn't have enough cached data to continue.
DescriptionFrederic Hornain
2015-02-20 18:22:43 UTC
Description of problem:
Well, I was currently installing docker on a new fresh RHEL 7 installation and I had the following error message :
[root@rhel7-docker ~]# yum install docker docker-registery
Loaded plugins: product-id, subscription-manager
https://cdn.redhat.com/content/eus/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
One of the configured repositories failed (Red Hat Enterprise Linux 7 Server - Extended Update Support (RPMs)),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Disable the repository, so yum won't use it by default. Yum will then
just ignore the repository until you permanently enable it again or use
--enablerepo for temporary usage:
yum-config-manager --disable rhel-7-server-eus-rpms
4. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=rhel-7-server-eus-rpms.skip_if_unavailable=true
failure: repodata/repomd.xml from rhel-7-server-eus-rpms: [Errno 256] No more mirrors to try.
https://cdn.redhat.com/content/eus/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
The workaround was to disable that specific repository.
[root@rhel7-docker ~]# subscription-manager repos --disable=rhel-7-server-eus-rpms
Well, I just wanted to let you know
Comment 3Masaki Furuta ( RH )
2015-03-09 02:35:04 UTC
Please also check Bug 1196182 Unavailable repo metadata rhel-7-server-eus-rpms for RHEL 7.0
Comment 4Valentina Mukhamedzhanova
2015-03-17 11:34:54 UTC
*** This bug has been marked as a duplicate of bug 1196182 ***