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 968496 - Unhandled python exception in reposync when an invalid repoid is specified
Summary: Unhandled python exception in reposync when an invalid repoid is specified
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum-utils
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Valentina Mukhamedzhanova
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-29 19:22 UTC by Maru Newby
Modified: 2015-10-12 15:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-12 15:08:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Maru Newby 2013-05-29 19:22:01 UTC
Description of problem:

Invoking reposync with an invalid repoid results in an unhandled python exception.

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

1.1.30-14.el6

How reproducible:

reposync --repoid=badrepoid


Actual results:

Traceback (most recent call last):
  File "/usr/bin/reposync", line 352, in <module>
    main()
  File "/usr/bin/reposync", line 349, in main
    sys.exit(exit_code)
UnboundLocalError: local variable 'exit_code' referenced before assignment

Expected results:

Either an error or a warning indicating that the repoid is not valid.

Additional info:

The exit_code variable is referenced on line 349 (sys.exit(exit_code)) but is not guaranteed to be defined if an invalid repo is specified.

Comment 2 Zdeněk Pavlas 2013-05-30 09:11:24 UTC
commit 6d3a95c63f3f000473f147bad230979fae00d029
Author: Zdeněk Pavlas <zpavlas>
Date:   Mon Dec 3 09:01:59 2012 +0100

    Initialize exit_code correctly.  BZ 882536

Comment 3 RHEL Program Management 2013-10-13 23:32:32 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 4 Karel Srot 2015-10-12 15:08:02 UTC
This bug is already fixed.

# reposync --repoid=badrepoid
# rpm -q yum-utils
yum-utils-1.1.30-30.el6.noarch


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