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 1296282 - Verifytree returns "error: no such file or directory"
Summary: Verifytree returns "error: no such file or directory"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: yum-utils
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Michal Domonkos
QA Contact: Eva Mrakova
URL:
Whiteboard:
Depends On:
Blocks: 1348995 1349433
TreeView+ depends on / blocked
 
Reported: 2016-01-06 19:25 UTC by Thom Carlin
Modified: 2020-08-13 08:21 UTC (History)
5 users (show)

Fixed In Version: yum-utils-1.1.31-39.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1333345 1348995 (view as bug list)
Environment:
Last Closed: 2016-11-04 00:14:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1099570 0 unspecified CLOSED Tracker Bug for RHCI related issues. 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2016:2187 0 normal SHIPPED_LIVE yum-utils bug fix and enhancement update 2016-11-03 13:18:35 UTC

Internal Links: 1099570

Description Thom Carlin 2016-01-06 19:25:56 UTC
Description of problem:

Verifytree tries to download a non-existent file, then reports an error.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Follow Sat 6 steps to create disconnected host up to katello-disconnected export...
2. expand-export.sh 
3. verifytree resulting repo(s)

Actual results:

...
  verifying comps.xml grammar with xmllint
error : No such file or directory
warning: failed to load external entity "http://cvs.fedoraproject.org/viewcvs/*checkout*/comps/comps.rng"
Relax-NG parser error : xmlRelaxNGParse: could not load http://cvs.fedoraproject.org/viewcvs/*checkout*/comps/comps.rng
Relax-NG schema http://cvs.fedoraproject.org/viewcvs/*checkout*/comps/comps.rng failed to compile
Checking all packages

Expected results:

...
  verifying comps.xml grammar with xmllint
Checking all packages

Additional info:

New location appears to be https://git.fedorahosted.org/cgit/comps.git/plain/comps.rng

Comment 2 Valentina Mukhamedzhanova 2016-02-09 18:45:18 UTC
Thom, could you upload a tarball with a sample repo to reproduce this problem? That would greatly increase the chance of having it addressed. Also, could you clarify why you consider the result you are getting to be a bug?

Comment 3 Thom Carlin 2016-02-09 18:50:44 UTC
It is a bug because we are shipping with a URL that will return a 404 from now on.

Comment 4 Valentina Mukhamedzhanova 2016-02-09 19:26:56 UTC
Ah, I see now that the URL is hardcoded in verifytree. Thank you for the report! Does replacing the URL with the new one fix the problem for you?

Comment 5 Thom Carlin 2016-02-09 19:40:29 UTC
Sorry, I didn't try it.  I would expect that it would....

Comment 6 Valentina Mukhamedzhanova 2016-02-09 20:20:21 UTC
I've tried replacing the URL, but it doesn't make much difference. xmllint fails even with a proper URL.

$ xmllint --noout --nowarning --relaxng https://git.fedorahosted.org/cgit/comps.git/plain/comps.rng /var/tmp/yum-root-aG929w/__tmp_trepo/gen/comps.xml
warning: failed to load external entity "https://git.fedorahosted.org/cgit/comps.git/plain/comps.rng"
Relax-NG parser error : xmlRelaxNGParse: could not load https://git.fedorahosted.org/cgit/comps.git/plain/comps.rng
Relax-NG schema https://git.fedorahosted.org/cgit/comps.git/plain/comps.rng failed to compile

Comment 7 Thom Carlin 2016-02-09 20:29:22 UTC
Checking the URLs inside that document: http://relaxng.org/ns/compatibility/annotations/1.0 gives a 404 also

Comment 10 Michal Domonkos 2016-04-29 11:12:01 UTC
(In reply to Valentina Mukhamedzhanova from comment #6)
> I've tried replacing the URL, but it doesn't make much difference. xmllint
> fails even with a proper URL.

The reason for this is that xmllint doesn't support SSL and the new URL starts with https.  We can fix this by either downloading the comps.rng file ourselves or shipping the file along with the yum-utils rpm.

Comment 22 Michal Domonkos 2016-07-08 17:55:33 UTC
New PR with a fixup:
https://github.com/rpm-software-management/yum-utils/pull/11

Comment 29 errata-xmlrpc 2016-11-04 00:14:26 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2187.html


Note You need to log in before you can comment on or make changes to this bug.