| Bug ID | 1190567 |
|---|---|
| Summary | vmlinuz is no longer present on /boot/ breaking separate boot partitions |
| Classification | openSUSE |
| Product | openSUSE Tumbleweed |
| Version | Current |
| Hardware | Other |
| OS | Other |
| Status | NEW |
| Severity | Normal |
| Priority | P5 - None |
| Component | Kernel |
| Assignee | kernel-bugs@opensuse.org |
| Reporter | dcermak@suse.com |
| QA Contact | qa-bugs@suse.de |
| Found By | --- |
| Blocker | --- |
The kernel packaging in Tumbleweed changed "recently" (at some point in the last months): vmlinuz is no longer on /boot/ but is now in /usr/lib/modules. I guess that this has been introduced as part of the usrmerge effort. However, this breaks images build by kiwi that use a separate boot partition, as now all these symlinks are dead when booting from that separate partition. This leads to booting issues like: Loading Linux 5.14.1-1-default ... error: ../../grub-core/fs/fshelp.c:257:file `/vmlinuz-5.14.1-1-default' not found. Loading initial ramdisk ... error: ../../grub-core/loader/i386/linux.c:1053:you need to load the kernel first. Example disk image: - https://build.opensuse.org/package/show/Virtualization:Appliances:Images:Testing_x86:tumbleweed/test-image-lvm - https://build.opensuse.org/package/show/Virtualization:Appliances:Images:Testing_x86:tumbleweed/test-image-overlayroot