On Mon, 18 Jul 2022, 08:28:31 +0200, Felix Miata wrote:
Manfred Hollstein composed on 2022-07-18 01:56 (UTC-0400):
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.
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. Cheers. l8er manfred