I got an error message from a dnf upgrade: Tracer: Call to Tracer API ended unexpectedly: TypeError: update() takes 2 positional arguments but 3 were given. It is not a regression from installed python3, see https://bugs.mageia.org/show_bug.cgi?id=28408. I have seen this issue before on Cauldron, though sporadically. The transaction itself remains untouched. Version-Release number of selected components: dnf-plugins-core-4.0.19-1.mga8 python3-dnf-plugins-core-4.0.19-1.mga8 python3-dnf-plugins-extras-common-4.0.13-1.mga8 python3-dnf-plugin-snapper-4.0.13-1.mga8 python3-dnf-plugin-tracer-4.0.13-1.mga8 python3-dnf-plugin-versionlock-4.0.19-1.mga8 python3-tracer-0.7.1-4.mga8 tracer-0.7.1-4.mga8 tracer-common-0.7.1-4.mga8 Best regards, Ulrich
Created attachment 12448 [details] Logfile of said upgrade
Thank you for the report + log file. From which a couple of things: 1. The error occurred right at the end apparently when verifying 10/10; but that Verify was done *before* the others, 1/10... Trigger for the fault? 2. After the traceback, the log has: Please visit https://github.com/FrostyX/tracer/issues and submit the issue inviting an upstream report. Which I leave to Neal to judge. Assigning this to him for 'dnf'.
Assignee: bugsquad => ngompa13
(In reply to Lewis Smith from comment #2) > Thank you for the report + log file. From which a couple of things: > > 1. The error occurred right at the end apparently when verifying 10/10; but > that Verify was done *before* the others, 1/10... Trigger for the fault? > The error always happens after last verify, never between. The transaction is untouched and complete, to be seen with # dnf history. Tracer gives info which packages need reboot or new login.
I guess the issue occurs always when an upgrade of systemd is involved.
(In reply to Lewis Smith from comment #2) > Thank you for the report + log file. From which a couple of things: > > 1. The error occurred right at the end apparently when verifying 10/10; but > that Verify was done *before* the others, 1/10... Trigger for the fault? > > 2. After the traceback, the log has: > Please visit https://github.com/FrostyX/tracer/issues and submit the issue > inviting an upstream report. Which I leave to Neal to judge. > > Assigning this to him for 'dnf'. Your assessment is correct. This should be filed with tracer upstream.
Source RPM: (none) => tracer-0.7.1-4.mga8.src.rpm
I don't remember a problem when upgrading a test install mga7 upgrade to mga8 (pre release) Is this something to be noted in errata or https://wiki.mageia.org/en/Mageia_8_Release_Notes#Upgrading_online.2C_using_DNF_.28CLI.29 ?
CC: (none) => fri
(In reply to Morgan Leijström from comment #6) > I don't remember a problem when upgrading a test install mga7 upgrade to > mga8 (pre release) > > Is this something to be noted in errata or > https://wiki.mageia.org/en/Mageia_8_Release_Notes#Upgrading_online. > 2C_using_DNF_.28CLI.29 > > ? No, tracer is not installed by default. The transaction itself is untouched and complete.
Created attachment 12595 [details] Log of systemd-upgrade Another occurrence with an error message not seen before in Cauldron. Installed components dnf-plugins-core-4.0.19-2.mga9 python3-dnf-plugins-core-4.0.19-2.mga9 python3-dnf-plugins-extras-common-4.0.13-2.mga9 python3-dnf-plugin-system-upgrade-4.0.13-2.mga9 python3-dnf-plugin-tracer-4.0.13-2.mga9 python3-dnf-plugin-versionlock-4.0.19-2.mga9 python3-tracer-0.7.5-1.mga9 tracer-0.7.5-1.mga9 tracer-common-0.7.5-1.mga9
https://bugs.mageia.org/show_bug.cgi?id=29168#c6 Another occurrence. See attachment to comment.
Upstream bug report apparently exists, and I've linked this to that one: https://github.com/FrostyX/tracer/issues/156
URL: (none) => https://github.com/FrostyX/tracer/issues/156
I don't recall that I have seen this issue in Cauldron for months now. Closing, will reopen if occurs again. Ulrich
Version: 8 => CauldronStatus: NEW => RESOLVEDResolution: (none) => OLD