Bug 1700551

Summary: `dnf system-upgrade download` f29→f30 shows a traceback
Product: [Fedora] Fedora Reporter: Christian Stadelmann <fedora>
Component: dnfAssignee: rpm-software-management
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: awilliam, dmach, jmracek, jrohel, mblaha, mhatina, packaging-team-maint, pkratoch, rpm-software-management, vmukhame
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-16 21:43:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Christian Stadelmann 2019-04-16 20:57:50 UTC 
Description of problem:
When running `dnf system-upgrade download --releasever 30 --setopt='module_platform_id=platform:f30'`, I get a traceback after the transaction check.

Version-Release number of selected component (if applicable):
$ rpm -qa | grep dnf
python3-dnf-plugin-leaves-4.0.6-1.fc29.noarch
python3-dnf-plugins-extras-common-4.0.4-1.fc29.noarch
dnf-data-4.2.2-2.fc29.noarch
python3-dnf-4.2.2-2.fc29.noarch
python3-libdnf-0.28.1-1.fc29.x86_64
dnf-utils-4.0.6-1.fc29.noarch
dnf-plugins-core-4.0.6-1.fc29.noarch
dnf-automatic-4.2.2-2.fc29.noarch
python2-libdnf-0.28.1-1.fc29.x86_64
python3-dnf-plugin-system-upgrade-4.0.4-1.fc29.noarch
dnf-4.2.2-2.fc29.noarch
libdnf-0.28.1-1.fc29.x86_64
python2-dnf-4.2.2-2.fc29.noarch
python3-dnf-plugins-core-4.0.6-1.fc29.noarch

How reproducible:
always on the single machine I tested.

Steps to Reproduce:
1. `dnf system-upgrade download --releasever 30 --setopt='module_platform_id=platform:f30'`
2. have a look at the output

Actual results:
After transaction check and test, during "Transaktion wird ausgeführt" (German for "Running transaction", see dnf/base.py:881), I get this traceback:

  File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 260, in callback
    self._elemProgress(key, amount)
  File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 303, in _elemProgress
    transaction_list = self._extract_cbkey(key)
  File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 244, in _extract_cbkey
    raise RuntimeError("TransactionItem not found for key: %s" % cbkey)
RuntimeError: TransactionItem not found for key: rtkit

Expected results:
No traceback

Additional info:
I have no clue whether this actually is a real issue or just cosmetic stuff. dnf system-upgrade tells me later: "Download complete! Use 'dnf system-upgrade reboot' to start the upgrade." So it does not seem to know that it has thrown an error.
Comment 1 Adam Williamson 2019-04-16 21:12:29 UTC 
What does 'rpm -q rtkit' say?
Comment 2 Christian Stadelmann 2019-04-16 21:38:56 UTC 
(In reply to Adam Williamson from comment #1)
> What does 'rpm -q rtkit' say?

Good catch! It shows

$ rpm -q rtkit
rtkit-0.11-19.fc29.x86_64
rtkit-0.11-20.fc29.x86_64
Comment 3 Christian Stadelmann 2019-04-16 21:40:44 UTC 
Looks like I ran into fallout from https://bugzilla.redhat.com/show_bug.cgi?id=1637496.
Comment 4 Christian Stadelmann 2019-04-16 21:43:14 UTC 
(In reply to Christian Stadelmann from comment #3)
> Looks like I ran into fallout from
> https://bugzilla.redhat.com/show_bug.cgi?id=1637496.

That bug report also contains a workaround. Surely, this is no bug in dnf.

*** This bug has been marked as a duplicate of bug 1637496 ***