Bootloader type detection ignores the actual bootloader in use

Bug #1563737 reported by Jian Luo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snappy
Fix Released
Medium
Unassigned
initramfs-tools-ubuntu-core (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

I was trying to seed U-Boot on an x86 image. scripts/ubuntu-core-rootfs can not detect the bootloader actually in use. In my case, U-Boot will be completely ignored on x86. Snappy can however detect bootloader type successfully with other criteria on boot_partition instead of on rootmount, which is inconsistent with initramfs-tools-ubuntu-core.

initramfs-tools-ubuntu-core should either
1. take over system-boot mount and use /boot/uboot/uboot.env and /boot/grub/grub.cfg to detect the desired bootloader type, or
2. support bootloader type override through kernel cmdline, e.g. new parameter "snappy_bootloader=uboot"

Michael Vogt (mvo)
Changed in initramfs-tools-ubuntu-core (Ubuntu):
status: New → Triaged
Changed in snappy:
status: New → Triaged
importance: Undecided → Medium
Changed in initramfs-tools-ubuntu-core (Ubuntu):
importance: Undecided → Medium
Michael Vogt (mvo)
Changed in initramfs-tools-ubuntu-core (Ubuntu):
importance: Medium → Critical
status: Triaged → In Progress
Revision history for this message
Michael Vogt (mvo) wrote :

This is fixed in core 16

Changed in initramfs-tools-ubuntu-core (Ubuntu):
status: In Progress → Fix Released
Changed in snappy:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.