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.
DescriptionKashyap Chamarthy
2018-12-06 11:13:20 UTC
Running `dnf update` on a RHEL-8 guest (installed from the
'nightly-1590', built on 07SEP2018) results in the transaction itself
succeeding, but throws: "Errors occurred during transaction" on the
shell.
From the /var/log/dnf.log (full log in the attachment):
[...]
2018-12-06T09:39:58Z SUBDEBUG
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 64, in main
return _main(base, args, cli_class, option_parser_class)
File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 99, in _main
return cli_run(cli, base)
File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 123, in cli_run
ret = resolving(cli, base)
File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 154, in resolving
base.do_transaction(display=displays)
File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 249, in do_transaction
for tsi in trans:
dnf.exceptions.Error: Transaction failed
2018-12-06T09:39:58Z CRITICAL Error: Transaction failed
[...]
And from the /var/log/dnf.rpm.log (full log in the attachment):
[...]
2018-12-06T09:37:05Z ERROR Error in POSTUN scriptlet in rpm package bind-export-libs
2018-12-06T09:37:05Z ERROR Error in POSTUN scriptlet in rpm package bind-export-libs
[...]
When I say "transaction itself succeeded, I mean the subsequent runs of
`dnf clean all` && `dnf update` do _not_ result in any failures.
So there doesn't seem to be any real underlying error. But talking to
Jaroslav Mracek on IRC, he says that the exception is being raised in
the incorrect place, and suggested to file this bug.
Comment 1Kashyap Chamarthy
2018-12-06 11:17:01 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
Comment 17Red Hat Bugzilla
2023-09-14 04:43:26 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Running `dnf update` on a RHEL-8 guest (installed from the 'nightly-1590', built on 07SEP2018) results in the transaction itself succeeding, but throws: "Errors occurred during transaction" on the shell. From the /var/log/dnf.log (full log in the attachment): [...] 2018-12-06T09:39:58Z SUBDEBUG Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 64, in main return _main(base, args, cli_class, option_parser_class) File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 99, in _main return cli_run(cli, base) File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 123, in cli_run ret = resolving(cli, base) File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 154, in resolving base.do_transaction(display=displays) File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 249, in do_transaction for tsi in trans: dnf.exceptions.Error: Transaction failed 2018-12-06T09:39:58Z CRITICAL Error: Transaction failed [...] And from the /var/log/dnf.rpm.log (full log in the attachment): [...] 2018-12-06T09:37:05Z ERROR Error in POSTUN scriptlet in rpm package bind-export-libs 2018-12-06T09:37:05Z ERROR Error in POSTUN scriptlet in rpm package bind-export-libs [...] When I say "transaction itself succeeded, I mean the subsequent runs of `dnf clean all` && `dnf update` do _not_ result in any failures. So there doesn't seem to be any real underlying error. But talking to Jaroslav Mracek on IRC, he says that the exception is being raised in the incorrect place, and suggested to file this bug.