http://bugzilla.opensuse.org/show_bug.cgi?id=990701 Bug ID: 990701 Summary: Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers@forge.provo.novell.com Reporter: abittner@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I have the KOTD repo added to a pretty simple plain Leap 42.1 x64 machine. I did add this KOTD for a few months now. It always upgraded the kernels in the past within the KOTD branch. Recently it went from 4.7 rc1 to rc2, then another rc2 release and today zypper ref and zypper lu displayed that there would be a non rc2 (rtm i suppose) for 4.7 kernel. Zypper up installed this kernel but didnt activate this rtm one in the grub2 bootloader and thus didnt switch over after I just rebooted this machine. ---------- kernel-default-4.7.0-1.1.g24f30d5.x86_64 kernel-default-4.7.rc7-2.1.g152f160.x86_64 kernel-firmware-20160503-3.1.noarch ------ 1 | KOTD | KOTD | Yes | (r ) Yes | No | 100 | rpm-md | http://download.opensuse.org/repositories/Kernel:/HEAD/standard --------------- Linux linux 4.7.0-rc7-2.g152f160-default #1 SMP PREEMPT Thu Jul 21 12:38:47 UTC 2016 (152f160) x86_64 x86_64 x86_64 GNU/Linux ---------- There was a zypper and libzypp update just some days ago. I briefly read about some new zypper problems and discussion on the bugs list or somewhere. Maybe this is a bug within current zypper? ----- zypper-aptitude-1.12.44-12.1.noarch snapper-zypp-plugin-0.2.9.1-3.1.noarch libzypp-15.22.2-12.1.x86_64 zypper-1.12.44-12.1.x86_64 PackageKit-backend-zypp-1.0.7-3.5.x86_64 zypper-log-1.12.44-12.1.noarch zypp-plugin-python-0.5-4.2.x86_64 ----- How exactly does zypper replace the currently selected and in use kernel for grub2 config? How can I manually select which kernel package to use for grub2 when there are multiple installed as in this case? what config setting and where and how influences what stuff becomes added or replaced in the grub2 config? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.