[opensuse-factory] Purge-kernels.service not working anymore
Hi there I have just realized that purge-kernels at boot in TW does not work anymore (multiversion is enabled). In fact, after the removal of the purge-kernels scripts and service with dracut 049+git117.d3206e79 there is an additional package called 'purge-kernels-service', which has to be installed manually. Is this on purpose? On top of that, the new package/service fails on boot with purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2020-01-23 20:48:05 CET; 2min 11s ago Process: 1199 ExecStartPre=/bin/rm -f /boot/do_purge_kernels (code=exited, status=0/SUCCESS) Process: 1243 ExecStart=/usr/bin/zypper purge-kernels (code=exited, status=4) Main PID: 1243 (code=exited, status=4) Anyone else seeing this? Thank you. Regards, Frank -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 23.01.20 um 21:11 schrieb Frank Krüger:
Hi there
I have just realized that purge-kernels at boot in TW does not work anymore (multiversion is enabled). In fact, after the removal of the purge-kernels scripts and service with dracut 049+git117.d3206e79 there is an additional package called 'purge-kernels-service', which has to be installed manually. Is this on purpose?
On top of that, the new package/service fails on boot with
purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2020-01-23 20:48:05 CET; 2min 11s ago Process: 1199 ExecStartPre=/bin/rm -f /boot/do_purge_kernels (code=exited, status=0/SUCCESS) Process: 1243 ExecStart=/usr/bin/zypper purge-kernels (code=exited, status=4) Main PID: 1243 (code=exited, status=4)
Anyone else seeing this? Thank you.
Regards, Frank
FYI: https://bugzilla.opensuse.org/show_bug.cgi?id=1161620 Regards, Frank -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Frank Krüger wrote:
I have just realized that purge-kernels at boot in TW does not work anymore (multiversion is enabled).
Anyone else seeing this? Thank you.
Indeed, I just upgraded to 20200121, rebooted - no purge-kernels. And woodstock:~ # systemctl status purge-kernels.service Unit purge-kernels.service could not be found. (but the systemctl call it did auto-complete pu+TAB to purge-kernels.service) With the previous one (to 20200118) it had still worked. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 24. 01. 20, 11:07, Peter Suetterlin wrote:
Frank Krüger wrote:
I have just realized that purge-kernels at boot in TW does not work anymore (multiversion is enabled).
Anyone else seeing this? Thank you.
Indeed, I just upgraded to 20200121, rebooted - no purge-kernels. And woodstock:~ # systemctl status purge-kernels.service Unit purge-kernels.service could not be found.
(but the systemctl call it did auto-complete pu+TAB to purge-kernels.service)
That would be perhaps outcome of: https://bugzilla.suse.com/show_bug.cgi?id=1131629 It's a bug that /etc/systemd/system/multi-user.target.wants/purge-kernels.service is left as a dangling link. That's why TAB completion sees it, but systemctl doesn't. thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday, January 24, 2020 1:37:16 PM CET Jiri Slaby wrote:
On 24. 01. 20, 11:07, Peter Suetterlin wrote:
Frank Krüger wrote:
I have just realized that purge-kernels at boot in TW does not work anymore (multiversion is enabled).
Anyone else seeing this? Thank you.
Indeed, I just upgraded to 20200121, rebooted - no purge-kernels. And woodstock:~ # systemctl status purge-kernels.service Unit purge-kernels.service could not be found.
(but the systemctl call it did auto-complete pu+TAB to purge-kernels.service) That would be perhaps outcome of: https://bugzilla.suse.com/show_bug.cgi?id=1131629
It's a bug that /etc/systemd/system/multi-user.target.wants/purge-kernels.service is left as a dangling link. That's why TAB completion sees it, but systemctl doesn't.
thanks,
Jiri, in https://bugzilla.suse.com/show_bug.cgi?id=1131629 Michal Suchanek says that purge-kernels is now a part of zypper but the new purge-kernels.service file is not included in zypper. But there is a purge-kernels-service package in https://download.opensuse.org/tumbleweed/repo/oss/x86_64/purge-kernels-servi... that correctly calls "ExecStart=/usr/bin/zypper purge-kernels" but is not mentioned in the zypper.spec here https://build.opensuse.org/package/view_file/openSUSE:Factory/zypper/ zypper.spec?expand=1 Shouldn't the spec file contain a Requires: /usr/lib/systemd/system/purge-kernels.service or something similar like the package name? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2020-01-24 at 16:00 +0100, Andreas Prittwitz wrote:
but is not mentioned in the zypper.spec here
https://build.opensuse.org/package/view_file/openSUSE:Factory/zypper/ zypper.spec?expand=1
Shouldn't the spec file contain a
Requires: /usr/lib/systemd/system/purge-kernels.service
or something similar like the package name?
No - zypper should not require that service. In fact, the plan is for the base pattern to recommend the service to be present (it's imho not a hard require on a system) BUT: we faced a problem with the sequence things happen: during boot up, that service fires up at the same time the KDE session might start and the updater applet check for updates. And since PK and zypper never liked each other being run at the same time, PK will simply 'yell' with a big warning. The KDE Team is currently busy adjusting the notificiatin appled for KDE to be less intrusive in the case of the (expectable) database lock [0] Once this fix is ready, the purge-kernels-service will be added as recommends to the base patterns. Cheers, Dominique [0] http://bugzilla.opensuse.org/show_bug.cgi?id=1161501
On Friday, January 24, 2020 4:07:19 PM CET Dominique Leuenberger / DimStar wrote:
On Fri, 2020-01-24 at 16:00 +0100, Andreas Prittwitz wrote:
but is not mentioned in the zypper.spec here
https://build.opensuse.org/package/view_file/openSUSE:Factory/zypper/ zypper.spec?expand=1
Shouldn't the spec file contain a
Requires: /usr/lib/systemd/system/purge-kernels.service
or something similar like the package name?
No - zypper should not require that service. In fact, the plan is for the base pattern to recommend the service to be present (it's imho not a hard require on a system)
BUT: we faced a problem with the sequence things happen: during boot up, that service fires up at the same time the KDE session might start and the updater applet check for updates. And since PK and zypper never liked each other being run at the same time, PK will simply 'yell' with a big warning. The KDE Team is currently busy adjusting the notificiatin appled for KDE to be less intrusive in the case of the (expectable) database lock [0]
Once this fix is ready, the purge-kernels-service will be added as recommends to the base patterns.
Cheers, Dominique
Understood, thanks for the explanation Dominique. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Couldn't help it but mention purge-kernels.service doesn't work on it's own too because it has plain `zypper` in Exec stanza instead of `zypper --non-interactive` per zypper's own error message in the journal (see https://paste.opensuse.org/95163190). On Fri, Jan 24, 2020 at 6:08 PM Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:
On Fri, 2020-01-24 at 16:00 +0100, Andreas Prittwitz wrote:
but is not mentioned in the zypper.spec here
https://build.opensuse.org/package/view_file/openSUSE:Factory/zypper/ zypper.spec?expand=1
Shouldn't the spec file contain a
Requires: /usr/lib/systemd/system/purge-kernels.service
or something similar like the package name?
No - zypper should not require that service. In fact, the plan is for the base pattern to recommend the service to be present (it's imho not a hard require on a system)
BUT: we faced a problem with the sequence things happen: during boot up, that service fires up at the same time the KDE session might start and the updater applet check for updates. And since PK and zypper never liked each other being run at the same time, PK will simply 'yell' with a big warning. The KDE Team is currently busy adjusting the notificiatin appled for KDE to be less intrusive in the case of the (expectable) database lock [0]
Once this fix is ready, the purge-kernels-service will be added as recommends to the base patterns.
Cheers, Dominique
-- Regards, Andrei Dziahel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2020-01-24 at 19:19 +0300, Andrei Dziahel wrote:
Couldn't help it but mention purge-kernels.service doesn't work on it's own too because it has plain `zypper` in Exec stanza instead of `zypper --non-interactive` per zypper's own error message in the journal (see https://paste.opensuse.org/95163190).
Very likely that one increases the problem with the notification applet, as there is literally no chance that it could even have finished its task by the time PK comes up. I've seen a fix flying into staging already for that one though: https://build.opensuse.org/request/show/766917 So that issue will certainly be fixed in a snapshot early next week. Cheers, Dominique
participants (6)
-
Andreas Prittwitz -
Andrei Dziahel -
Dominique Leuenberger / DimStar -
Frank Krüger -
Jiri Slaby -
Peter Suetterlin