My opinion is that "Won't Fix" is not the correct action for this bug:
- it is an acknowledged issue in grub which is now resolved
- it is a regression in that previously functioning systems with a bpool configured according to guidelines stops working after upgrading to the latest Jammy HWE kernel when a pool level snapshot is created
- my failed attempt to workaround the problem using the package from 24.04 suggests that the forthcoming LTS release could be susceptible to this problem
My opinion is that "Won't Fix" is not the correct action for this bug:
- it is an acknowledged issue in grub which is now resolved
- it is a regression in that previously functioning systems with a bpool configured according to guidelines stops working after upgrading to the latest Jammy HWE kernel when a pool level snapshot is created
- my failed attempt to workaround the problem using the package from 24.04 suggests that the forthcoming LTS release could be susceptible to this problem
Related links: /bugs.launchpad .net/ubuntu/ +source/ grub2/+ bug/2041739 /ubuntuforums. org/showthread. php?t=2494397& p=14175278 /savannah. gnu.org/ bugs/index. php?64297 (bug still open, perhaps fixed without referencing it?)
- https:/
- https:/
- https:/