Please update the SRU template:
a) impact
The current impact section just mentions the wrong name of the unit, but not
the impact that this has on a user's system. grub is a critical component, and
we need to have a good reason to update it in a stable release.
b) test plan
The test plan is too much focused on the specific change (ordering, name of the
unit), instead of the resolution of the real world impact (once (a) is updated).
c) regression potential
systemd unit ordering is always tricky, prone to races of all sorts. Could this
update lead to an unbootable system? Or a delayed boot? Or something else?
Again, this also depends on a proper [impact] section.
d) please clarify the stonking status. From a quick check, it looks like
the same set of changes is applied there and currently in stonking-
unapproved. Please verify, and adjust the stonking bug task accordingly.
** Changed in: grub2 (Ubuntu Resolute)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2156423
Title:
Fix grub-initrd-fallback.service order
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2156423/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
