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.

Description of problem:
When some error happens with reposync util, long traceback is shown

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

How reproducible:
100%

Steps to Reproduce:
1. set some repository which has e.g. broken link in baseurl
2. run reposync # reposync --repoid=epel
3. see traceback 

Actual results:

~~~
# reposync --repoid=epel
Traceback (most recent call last):
  File "/bin/reposync", line 343, in <module>
<...>
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 897, in _getMetalink
    raise Errors.RepoError, msg
yum.Errors.RepoError: Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
~~~

Expected results:
Short error output is expected, this is how it looks in RHEL 6

~~~
# reposync --repoid=epel
Error setting up repositories: Cannot retrieve repository metadata (repomd.xml) for repository: epel. Please verify its path and try again
~~~

Additional info:

Right, this is because we don't handle exceptions from the my.doRepoSetup() call which leads to fetching the metadata on RHEL-7, see this commit:


commit a522869c21768d53c3861be9c0a2394a3930ad66
Author: Zdeněk Pavlas <zpavlas>
Date:   Wed Mar 28 15:59:26 2012 +0200

    retrieveAllMD(): parallel metadata downloading
    
    Metadata are downloaded in parallel just before postreposetup.
    This implements the reverting behavior.


The fix should be quite trivial.

*** Bug 1482899 has been marked as a duplicate of this bug. ***

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://access.redhat.com/errata/RHBA-2019:2288