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.
DescriptionMatthew Mosesohn
2011-11-18 18:50:49 UTC
Description of problem:
If you have 1 repo enabled that points to a repo that no longer exists, you can't run any yum install or update.
Version-Release number of selected component (if applicable):
yum-3.2.29-22.el6
How reproducible:
Always
Steps to Reproduce:
1. Create a repo that points to an invalid URL that will return a 404 error
2. yum update
Actual results:
[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404"
Expected results:
The repo that has a 404 error should be skipped and attempt to try to continue and attempt the operation based on the remaining repos that work.
Additional info:
This will cause package installs triggered by RHN or Satellite to fail if there is any repo that points to a 404 URL
This is intentional, in that the policy is it's better to do nothing than do the wrong thing.
If this kind of thing is likely with particular repos. though, in RHEL-6 you can specify "skip_if_unavailable=true" in the .repo file ... and that repo. will be automatically disabled.
James,
There is no global option you can specify in yum.conf which can set this globally. It's important to provide a mechanism to ensure that Satellite can install packages on a system, regardless of the less-than-intelligent sysadmin who happens to have root on the host. If someone goes and finds a random repo for their favorite software, and then the tree where that repo disappears, there's little the Satellite admin can do to install or update packages on the host.
What is the main reason behind preventing the creation of a global skip_if_unavailable option? It would really add a lot of value to yum.
There are lots of things a user can do which will break yum, or RHN. They can also do things like enable a repo. that obsoletes something which breaks RHN repos. ... or even just has bad deps. (so "yum upgrade" fails, even though the repo. is "working").
From the Satellite/RHN side one workaround that users might like is a mode where you try to do the operation but with _only_ RHN repos. enabled (or even, only some of them).
From the yum side, the skip option is basically a hacky getout to say "this repo. is kind of worthless, I don't mind if it randomly goes away" ... saying that for all the repos. by default would be _very_ strange.
Hi,
I sent a patch to yum upstream which handles this case, I think
you should be able to do:
yum --setopt='*.skip_if_unavailable=1' update
and it will make all repos have that value for run time.
or
yum-config-manager --setopt='*.skip_if_unavailable=1' --save
and it will save that setting to all repos defined for that system.
It's a pretty non-invasive patch and it shouldn't break anyone else's cases since it's not like a repo can be named with globs anyway.