Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionPavla Kratochvilova
2019-08-05 06:20:38 UTC
+++ This bug was initially created as a clone of Bug #1693511 +++
Version-Release number of selected component:
dnf-4.2.1-1.fc29
Additional info:
reporter: libreport-2.10.0
cmdline: /usr/bin/python3 /usr/bin/dnf distro-sync
crash_function: endTransaction
exception_type: RuntimeError
executable: /usr/bin/dnf
interpreter: python3-3.7.2-5.fc29.x86_64
kernel: 5.0.4-200.fc29.x86_64
runlevel: N 5
type: Python3
uid: 0
Truncated backtrace:
transaction.py:758:endTransaction:RuntimeError: TransactionItem state is not set: nodejs-1:10.15.0-1.fc29.x86_64
Traceback (most recent call last):
File "/usr/bin/dnf", line 58, in <module>
main.user_main(sys.argv[1:], exit_code=True)
File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 192, in user_main
errcode = main(args)
File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 64, in main
return _main(base, args, cli_class, option_parser_class)
File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 99, in _main
return cli_run(cli, base)
File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 123, in cli_run
ret = resolving(cli, base)
File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 167, in resolving
base.do_transaction(display=displays)
File "/usr/lib/python3.7/site-packages/dnf/cli/cli.py", line 225, in do_transaction
tid = super(BaseCli, self).do_transaction(display)
File "/usr/lib/python3.7/site-packages/dnf/base.py", line 882, in do_transaction
tid = self._run_transaction(cb=cb)
File "/usr/lib/python3.7/site-packages/dnf/base.py", line 1009, in _run_transaction
self.history.end(rpmdbv, 2, errors=herrors)
File "/usr/lib/python3.7/site-packages/dnf/db/history.py", line 504, in end
bool(return_code)
File "/usr/lib64/python3.7/site-packages/libdnf/transaction.py", line 758, in endTransaction
return _transaction.Swdb_endTransaction(self, dtEnd, rpmdbVersionEnd, state)
RuntimeError: TransactionItem state is not set: nodejs-1:10.15.0-1.fc29.x86_64
Local variables in innermost frame:
self: <libdnf.transaction.Swdb; proxy of <Swig Object of type 'libdnf::Swdb *' at 0x7f597ba67390> >
dtEnd: 1553714591
rpmdbVersionEnd: '3364:19201e723fec3b8b5d3b625c84e6be03cb6a7f0e'
state: False
--- Additional comment from on 2019-03-28 03:24:20 UTC ---
--- Additional comment from on 2019-03-28 03:24:21 UTC ---
--- Additional comment from on 2019-03-28 03:24:22 UTC ---
--- Additional comment from on 2019-03-28 03:24:26 UTC ---
--- Additional comment from on 2019-03-28 03:24:27 UTC ---
--- Additional comment from on 2019-03-28 03:24:28 UTC ---
--- Additional comment from on 2019-03-28 03:24:29 UTC ---
--- Additional comment from on 2019-03-28 03:24:30 UTC ---
--- Additional comment from Daniel Mach on 2019-04-01 11:23:10 UTC ---
Could you provide a list of RPMs before the transaction or information about the transaction that failed?
You can achieve that by:
* providing /var/log/dnf.log (whole or relevant part)
* providing output of relevant `dnf history info <id>`
* where id is a transaction id from `dnf history list`
* or you can alternatively use 'last', 'last-1', 'last-2', ...
--- Additional comment from Daniel Mach on 2019-07-02 12:15:35 UTC ---
--- Additional comment from Daniel Mach on 2019-07-02 12:15:49 UTC ---
--- Additional comment from Daniel Mach on 2019-07-02 12:16:42 UTC ---
--- Additional comment from Daniel Mach on 2019-07-02 12:16:55 UTC ---
--- Additional comment from Daniel Mach on 2019-07-02 12:17:11 UTC ---
--- Additional comment from Daniel Mach on 2019-07-02 12:17:23 UTC ---
--- Additional comment from Daniel Mach on 2019-07-02 12:17:25 UTC ---
--- Additional comment from Daniel Mach on 2019-07-02 12:17:28 UTC ---
--- Additional comment from Daniel Mach on 2019-07-02 12:17:35 UTC ---
--- Additional comment from Daniel Mach on 2019-07-02 12:19:44 UTC ---
--- Additional comment from Daniel Mach on 2019-07-02 12:20:43 UTC ---
PR: https://github.com/rpm-software-management/dnf/pull/1415
Comment 2Pavla Kratochvilova
2019-08-07 07:37:00 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://access.redhat.com/errata/RHSA-2019:3583