Verification performed on several VMs with configurations covering:

* "normal" (gpt partitioning, ext4 root, /boot as dir under root) -- passed
* "dos" (same but with dos partitioning) -- passed
* "btrfs" (gpt partitioning, btrfs root, /boot as dir) -- blocked (correctly)
* "lvm" (root on lvm, /boot on separate ext2 partition) -- success
* "lvmboot" (root on lvm, /boot as dir) -- blocked (correctly)
* "pi" (standard ubuntu server image on a Raspberry Pi) -- success
* "pi-btrfs" (ubuntu server image converted to btrfs on a Raspberry Pi) -- 
success (correctly, doesn't use GRUB)
* "raid1" (root and /boot on mdadm RAID1 devices, gpt partitioning) -- success
* "luks" (gpt partitioning, root on ext4 inside LUKS, /boot on separate ext4 
partition) -- success

We're not going to have the time to test absolutely every combination
here, but the above represents a pretty broad cross-section of
configurations, with several corner cases (e.g. btrfs on a non-GRUB
config, lvm with /boot separate, etc.) and so far everything's behaved
as expected. Tentatively marking this verification succeeded, but if
anyone wants to weigh in with more testing, please do!

** Tags removed: verification-needed-stonking
** Tags added: verification-done-stonking

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2170211

Title:
  [SRU] Systems using niche /boot configurations won't be able to
  upgrade from 26.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2170211/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to