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 852643 - yum doesn't follow skip_if_unavailable when downloading filelists
Summary: yum doesn't follow skip_if_unavailable when downloading filelists
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum
Version: 6.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: James Antill
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-29 08:13 UTC by Karel Srot
Modified: 2014-01-21 06:25 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-29 14:15:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Karel Srot 2012-08-29 08:13:49 UTC 
Description of problem:

# yum install openssl-devel 
Loaded plugins: security
http://XXX.redhat.com/repo/repodata/repomd.xml: [Errno 14] PYCURL ERROR 7 - "couldn't connect to host"
Trying other mirror.
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package openssl-devel.x86_64 0:1.0.0-20.el6 will be updated
---> Package openssl-devel.x86_64 0:1.0.0-20.el6_2.5 will be an update
--> Processing Dependency: openssl = 1.0.0-20.el6_2.5 for package: openssl-devel-1.0.0-20.el6_2.5.x86_64
--> Running transaction check
---> Package openssl.x86_64 0:1.0.0-20.el6 will be updated
---> Package openssl.x86_64 0:1.0.0-20.el6_2.5 will be an update
http://XXX.redhat.com/repo/repodata/filelists.xml.gz: [Errno 14] PYCURL ERROR 7 - "couldn't connect to host"
Trying other mirror.
Error: failure: repodata/filelists.xml.gz from qa: [Errno 256] No more mirrors to try.
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest



# cat /etc/yum.repos.d/qa.repo 
[qa]
name=QA
baseurl=http://XXX.redhat.com/repo/
enabled=1
skip_if_unavailable=1
gpgcheck=0


Version-Release number of selected component (if applicable):
yum-3.2.29-30.el6.noarch


How reproducible:
always

Steps to Reproduce:
1. ensure you have updated metadata for a repo (but missing filelists.xml.gz)
2. cut-off the machine serving the repo (or delete the repo)
3. initiate action that requires filelist downloading, e.g. yum install /path/that/does/not/exist
Comment 1 James Antill 2012-08-29 14:15:31 UTC 
 You can add filelists to mdpolicy, to work around this. But after the repo. has been accepted we can't easily just remove it again (esp. mid. depsolve).
Comment 2 Karel Srot 2012-08-29 14:52:44 UTC 
Would it be at least possible to propose "valid" solution, e.g. clean repo metadata or disable the repo? Proposed --skip-broken is useless.
Comment 3 James Antill 2012-08-29 20:42:59 UTC 
 Outputting a better message might be hard, the one given is the generic "something failed in depsolving" message ... we'd have to know that the failure was due to missing filelists, and which repo. (we might have that info. and it might be trivial, haven't looked atm).

 In theory we could also do something like "if we fail a filelists/package request then immediately remove the repodata" at which point the next time you ran yum it'd have to get a new repomd/primary or fail. Not sure that's great default behaviour though, and it'd suck a lot for non skip_if_unavail repos.
Note You need to log in before you can comment on or make changes to this bug.