Bugzilla – Bug 1222044
zypper %posttrans fails with "Failed to start jobs"
Last modified: 2024-03-27 16:14:41 UTC
Created attachment 873853 [details] zypper.log Upgrading from TW Snapshot 20240321 to 20240325 with zypper -v dup had the following output at the end: Ausgabe des Skripts %posttrans(zypper-1.14.70-1.1.x86_64): Failed to start jobs: Failed to enqueue some jobs, see logs for details: No such file or directory Nach-Transaktions-Skripte werden ausgeführt ..............................................................................................................................................................................................[fertig] CommitResult (total 432, done 432, error 0, skipped 0, updateMessages 0)
@Fabian No clue where the message comes from. I even tried a find /usr/bin /usr/lib64/ -type f | while read X; do echo "===== $X ====="; strings "$X" | grep jobs; done | less on my TW but did not find a matching text.
My own dup on TW did not report anything.
It's actually zypper's output being very misleading here. I narrowed it down to the update of the bluez package. Installing that with rpm -vvv shows: D: %transfiletriggerin(systemd-255.4-1.2.x86_64): running <lua> scriptlet. Failed to start jobs: Failed to enqueue some jobs, see logs for details: No such file or directory Apparently zypper attributes the transfiletriggerin execution to the zypper package. I'll have a look at why systemctl reload-or-restart fails weirdly and open another bug for that.
(In reply to Fabian Vogt from comment #3) > It's actually zypper's output being very misleading here. It's just the captured stderr of 'rpm --runposttrans' > I narrowed it down to the update of the bluez package. Installing that with > rpm -vvv shows: If you can attach the `rpm -vvv` output, I can check why it's shown at the wrong place.
Created attachment 873865 [details] rpm -vvv --reinstall bluez.rpm