Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1466649 - [DNF] rpm.RPMCALLBACK_ELEM_PROGRESS does not exist
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rpm (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: pre-dev-freeze
: ---
Assigned To: Igor Gnatenko
Jan Blazek
: 1466768 (view as bug list)
Depends On:
Blocks: 1461652 1465896 1466368
  Show dependency treegraph
Reported: 2017-06-30 03:19 EDT by Daniel Mach
Modified: 2018-04-10 11:59 EDT (History)
6 users (show)

See Also:
Fixed In Version: rpm-4.11.3-27.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-04-10 11:58:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0877 None None None 2018-04-10 11:59 EDT

  None (edit)
Description Daniel Mach 2017-06-30 03:19:32 EDT
This currently blocks DNF running on RHEL 7.
The feature has to be either backported into RPM (preferred) or we need to find a workaround in the DNF code.

  File "/usr/lib/python2.7/site-packages/dnf/yum/rpmtrans.py", line 425, in callback
    elif what == rpm.RPMCALLBACK_ELEM_PROGRESS:
AttributeError: 'module' object has no attribute 'RPMCALLBACK_ELEM_PROGRESS'
Comment 1 Panu Matilainen 2017-06-30 03:40:41 EDT
This should be fairly trivial to backport.
Comment 2 Panu Matilainen 2017-06-30 03:42:53 EDT
For reference, the relevant upstream commits are:
Comment 3 Panu Matilainen 2017-06-30 08:23:30 EDT
*** Bug 1466768 has been marked as a duplicate of this bug. ***
Comment 11 errata-xmlrpc 2018-04-10 11:58:38 EDT
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.


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