[Bug 2002029] [NEW] 10_linux_zfs fails if PRETTY_NAME not found

[Michael Charles Adams]

Public bug reported:

If a bootable zfs root dataset does not have "PRETTY_NAME" set in
/etc/os-release; update-grub fails.

This applies to all ubuntu distributions that have /etc/grub.d/10_linux_zfs
Previously I have hacked 10_linux_zfs with (pseudocode) if prettyname not set; set prettyname to "prettyname not set; root dataset is ..."
However this should be fixed upstream as more and more users use zfs datasets for multiboot (multiple distributions) or zfs boot environments (iterations of a distribution)

Background:
Even though I have moved to zfsbootmenu; overall systems requires update-grub to work.
Ubuntu latests LTS is the only bootable distribution on an ext4 partition for backup in all my systems. Other distributions for dev testing including bionic (server), focal (server), jammy, lunar, kali, kaisen, void, mx, fedora, artix-s6, arch*... are in zpool root datasets bootable by zfsbootmenu; and by grub with a backup bpool (which zfsbootmenu does not require, and is a pain to upkeep but required for failsafe). However not all such distributions have "PRETTY_NAME" in /etc/os-release
[distos without zfs-latest (2.1.17) such as bionic, focal, fedora... were installed to ext4; git openzfs/zfslatest built from source; then rsynced into the relevant zfs dataset, arch-chroot, genfstab, update-initramfs... etc]

** Affects: grub2 (Ubuntu)
     Importance: Undecided
         Status: New

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

Title:
  10_linux_zfs fails if PRETTY_NAME not found

Status in grub2 package in Ubuntu:
  New

Bug description:
  If a bootable zfs root dataset does not have "PRETTY_NAME" set in
  /etc/os-release; update-grub fails.

  This applies to all ubuntu distributions that have /etc/grub.d/10_linux_zfs
  Previously I have hacked 10_linux_zfs with (pseudocode) if prettyname not set; set prettyname to "prettyname not set; root dataset is ..."
  However this should be fixed upstream as more and more users use zfs datasets for multiboot (multiple distributions) or zfs boot environments (iterations of a distribution)

  Background:
  Even though I have moved to zfsbootmenu; overall systems requires update-grub to work.
  Ubuntu latests LTS is the only bootable distribution on an ext4 partition for backup in all my systems. Other distributions for dev testing including bionic (server), focal (server), jammy, lunar, kali, kaisen, void, mx, fedora, artix-s6, arch*... are in zpool root datasets bootable by zfsbootmenu; and by grub with a backup bpool (which zfsbootmenu does not require, and is a pain to upkeep but required for failsafe). However not all such distributions have "PRETTY_NAME" in /etc/os-release
  [distos without zfs-latest (2.1.17) such as bionic, focal, fedora... were installed to ext4; git openzfs/zfslatest built from source; then rsynced into the relevant zfs dataset, arch-chroot, genfstab, update-initramfs... etc]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2002029/+subscriptions