Manfred Hollstein composed on 2022-07-18 08:42 (UTC+0200):
Felix Miata wrote:
Manfred Hollstein composed on 2022-07-18 07:56 (UTC+0200):
Felix Miata wrote:
Felix Miata composed on 2022-07-15 19:20 (UTC-0400):
Is $SUBJECT what was supposed to happen?
Prior TW version was 20220630. Newest kernel installed prior to 5.18.9-2 was 5.17.9-1.
June/July portion of /var/log/zypp/history: https://paste.opensuse.org/74203728
Just happened again on dup from 20220613 to 20220714. Latest previous kernel was 5.18.2. :(
no problems here, all latest dups left all kernels installed. What does /etc/zypp/zypp.conf contain for multiversion.kernels? This is what I have here:
# grep multi /etc/zypp/zypp.conf | egrep -v '^#' multiversion = provides:multiversion(kernel) multiversion.kernels = latest,latest-1,running,oldest
Same here.
I forgot to mention, because I keep kernels locked, none added, none removed, unless and until I choose, this is/was a particularly huge surprise: # grep -B3 kernel /etc/zypp/locks type: package match_type: glob case_sensitive: on solvable_name: kernel-de* -- type: package match_type: glob case_sensitive: on solvable_name: kernel-firmwar?
I know rpm doesn't pay any attention to zypp locks, but I don't recall ever seeing this kind of burn, leaving no kernel to fall back on if the fresh one fails to boot.
I do remember such a problem - it was caused by "zypper purge-kernels" which happily removed all other kernels than the current one. This is why I disabled purge-kernels.service and also always remove the file /boot/do_purge_kernels after every "zypper dup". Don't know if this is actually still necessary, but could explain what you are seeing now.
AFAIK, do_purge_kernels is run /after/ booting the newest kernel the first time. That's not what happened here. I too have purge-kernels.service disabled, and masked. I also remove /boot/do_purge_kernels every time I see it, which normally follows immediately after a new kernel installation completes, when I goto /boot/ to adjust the symlinks, all but one of which for kernels are now dead: # ls -Gg ini* lrwxrwxrwx 1 23 Jul 18 01:09 initrd -> initrd-5.18.9-2-default -rw------- 1 16564455 Jan 18 01:21 initrd-5.15.12-1-default -rw------- 1 15086540 May 17 03:23 initrd-5.16.15-1-default -rw------- 1 15306732 Jun 14 18:40 initrd-5.17.9-1-default -rw------- 1 16203164 Jul 18 01:10 initrd-5.18.9-2-default -rw------- 1 14107304 Sep 30 2020 initrd-5.7.11-1-default lrwxrwxrwx 1 23 Jul 18 01:09 initrd-cur -> initrd-5.18.9-2-default lrwxrwxrwx 1 23 Jun 14 18:40 initrd-prv -> initrd-5.17.9-1-default lrwxrwxrwx 1 24 May 17 03:22 initrd-prv2 -> initrd-5.16.15-1-default lrwxrwxrwx 1 24 Jan 18 01:20 initrd-prv3 -> initrd-5.15.12-1-default lrwxrwxrwx 1 23 Sep 30 2020 initrd-prv8 -> initrd-5.7.11-1-default The initrds are still there due to immutable flags I attach after each has proven bootable.
I also forgot to mention, I installed 5.18.9-2 using rpm -ivh, which didn't mention anything about any plan to remove anything that caught my attention. :(
I don't have any locks, but I protect the kernels differently as described above. -- Evolution as taught in public schools is, like religion, based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata