| 2020-10-26 14:30:52 |
Dimitri John Ledkov |
bug |
|
|
added bug |
| 2020-10-26 14:36:16 |
Dimitri John Ledkov |
description |
[Impact]
* Sometimes it is not obvious why initrdless boot is generated; when is it attempted; and when it fails and boots with initrd.
* Improve UX by leaving breadcrumbs and emit messages about initrdless boot, in more places
[Test Case]
* Boot system with initrdless boot (such as modern AWS images)
* Upgrade to new grub package
* Reboot
* Observe the following:
1. Upon `sudo update-grub`, message is emitted that initrdless boot will be attempted
2. Inspecting /boot/grub/grub.cfg, there are comments that initrdless boot will be attempted
3. Inspecting console log, there are echo message from grub about attempting initrdless boot.
* Install linux-generic kernel flavour; and remove aws kernel flavour, reboot.
* Observe in the console log
1. There should be message about attempting initrdless boot
2. kernel panic
3. message about initrdless boot failing and attempting to boot with initrd
[Regression Potential]
* This change adds a few more user visible message, without translations. The actual behaviour that is happening is unchanged. This simply better notifies users about what is happening, and can be inspected interactively, statically, and from boot logs.
[Other Info]
* CPC requested these UX improvements, as there have been concerns that users are failing to discover why initrdless boot is happening; or failing; and how to effect it. |
[Impact]
* Sometimes it is not obvious why initrdless boot is generated; when is it attempted; and when it fails and boots with initrd.
* Improve UX by leaving breadcrumbs and emit messages about initrdless boot, in more places
[Test Case]
* Boot system with initrdless boot (such as AWS nitro-based instance type, i.e. c5.large)
* Upgrade to new grub package
* Reboot
* Observe the following:
1. Upon `sudo update-grub`, message is emitted that initrdless boot will be attempted
2. Inspecting /boot/grub/grub.cfg, there are comments that initrdless boot will be attempted
3. Inspecting console log, there are echo message from grub about attempting initrdless boot.
* Install linux-generic kernel flavour; and remove aws kernel flavour, reboot.
* Observe in the console log
1. There should be message about attempting initrdless boot
2. kernel panic
3. message about initrdless boot failing and attempting to boot with initrd
[Regression Potential]
* This change adds a few more user visible message, without translations. The actual behaviour that is happening is unchanged. This simply better notifies users about what is happening, and can be inspected interactively, statically, and from boot logs.
[Other Info]
* CPC requested these UX improvements, as there have been concerns that users are failing to discover why initrdless boot is happening; or failing; and how to effect it. |
|
| 2020-10-27 10:37:53 |
Dimitri John Ledkov |
description |
[Impact]
* Sometimes it is not obvious why initrdless boot is generated; when is it attempted; and when it fails and boots with initrd.
* Improve UX by leaving breadcrumbs and emit messages about initrdless boot, in more places
[Test Case]
* Boot system with initrdless boot (such as AWS nitro-based instance type, i.e. c5.large)
* Upgrade to new grub package
* Reboot
* Observe the following:
1. Upon `sudo update-grub`, message is emitted that initrdless boot will be attempted
2. Inspecting /boot/grub/grub.cfg, there are comments that initrdless boot will be attempted
3. Inspecting console log, there are echo message from grub about attempting initrdless boot.
* Install linux-generic kernel flavour; and remove aws kernel flavour, reboot.
* Observe in the console log
1. There should be message about attempting initrdless boot
2. kernel panic
3. message about initrdless boot failing and attempting to boot with initrd
[Regression Potential]
* This change adds a few more user visible message, without translations. The actual behaviour that is happening is unchanged. This simply better notifies users about what is happening, and can be inspected interactively, statically, and from boot logs.
[Other Info]
* CPC requested these UX improvements, as there have been concerns that users are failing to discover why initrdless boot is happening; or failing; and how to effect it. |
[Impact]
* Sometimes it is not obvious why initrdless boot is generated; when is it attempted; and when it fails and boots with initrd.
* Improve UX by leaving breadcrumbs and emit messages about initrdless boot, in more places
[Test Case]
* Boot system with initrdless boot
- for example minimal cloud image from https://cloud-images.ubuntu.com/minimal/releases/
- boot without graphical terminal, i.e. -nographics qemu option
* Upgrade to new grub package
* Uncomment GRUB_TERMINAL=console in /etc/default/grub
1. Call `sudo update-grub`, a message should be emitted that initrdless boot will be attempted.
2. Inspecting /boot/grub/grub.cfg, there are comments that initrdless boot will be attempted
* Reboot
* Observe the following:
3. Inspecting console log, there are echo message from grub about attempting initrdless boot.
* Install linux-generic kernel flavour; and remove kvm kernel flavour, reboot.
* Observe in the console log
1. There should be message about attempting initrdless boot
2. kernel panic
3. message about initrdless boot failing and attempting to boot with initrd
[Regression Potential]
* This change adds a few more user visible message, without translations. The actual behaviour that is happening is unchanged. This simply better notifies users about what is happening, and can be inspected interactively, statically, and from boot logs.
[Other Info]
* CPC requested these UX improvements, as there have been concerns that users are failing to discover why initrdless boot is happening; or failing; and how to effect it. |
|
| 2020-10-27 13:17:30 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~xnox/grub/+git/grub/+merge/392865 |
|
| 2020-10-27 13:17:41 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~xnox/grub/+git/grub/+merge/392866 |
|
| 2021-01-04 16:04:41 |
Launchpad Janitor |
grub2 (Ubuntu): status |
New |
Fix Released |
|
| 2021-08-12 09:22:50 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/407003 |
|
| 2021-08-12 09:39:42 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Focal |
|
| 2021-08-12 09:39:42 |
Julian Andres Klode |
bug task added |
|
grub2 (Ubuntu Focal) |
|
| 2021-08-12 09:39:49 |
Julian Andres Klode |
grub2 (Ubuntu Focal): milestone |
|
ubuntu-20.04.3 |
|
| 2021-08-12 09:41:31 |
Julian Andres Klode |
description |
[Impact]
* Sometimes it is not obvious why initrdless boot is generated; when is it attempted; and when it fails and boots with initrd.
* Improve UX by leaving breadcrumbs and emit messages about initrdless boot, in more places
[Test Case]
* Boot system with initrdless boot
- for example minimal cloud image from https://cloud-images.ubuntu.com/minimal/releases/
- boot without graphical terminal, i.e. -nographics qemu option
* Upgrade to new grub package
* Uncomment GRUB_TERMINAL=console in /etc/default/grub
1. Call `sudo update-grub`, a message should be emitted that initrdless boot will be attempted.
2. Inspecting /boot/grub/grub.cfg, there are comments that initrdless boot will be attempted
* Reboot
* Observe the following:
3. Inspecting console log, there are echo message from grub about attempting initrdless boot.
* Install linux-generic kernel flavour; and remove kvm kernel flavour, reboot.
* Observe in the console log
1. There should be message about attempting initrdless boot
2. kernel panic
3. message about initrdless boot failing and attempting to boot with initrd
[Regression Potential]
* This change adds a few more user visible message, without translations. The actual behaviour that is happening is unchanged. This simply better notifies users about what is happening, and can be inspected interactively, statically, and from boot logs.
[Other Info]
* CPC requested these UX improvements, as there have been concerns that users are failing to discover why initrdless boot is happening; or failing; and how to effect it. |
[Impact]
(sort of prerequisite of bug 1929860 to avoid having to edit the patches and possibly introduce bugs that way)
* Sometimes it is not obvious why initrdless boot is generated; when is it attempted; and when it fails and boots with initrd.
* Improve UX by leaving breadcrumbs and emit messages about initrdless boot, in more places
[Test Case]
* Boot system with initrdless boot
- for example minimal cloud image from https://cloud-images.ubuntu.com/minimal/releases/
- boot without graphical terminal, i.e. -nographics qemu option
* Upgrade to new grub package
* Uncomment GRUB_TERMINAL=console in /etc/default/grub
1. Call `sudo update-grub`, a message should be emitted that initrdless boot will be attempted.
2. Inspecting /boot/grub/grub.cfg, there are comments that initrdless boot will be attempted
* Reboot
* Observe the following:
3. Inspecting console log, there are echo message from grub about attempting initrdless boot.
* Install linux-generic kernel flavour; and remove kvm kernel flavour, reboot.
* Observe in the console log
1. There should be message about attempting initrdless boot
2. kernel panic
3. message about initrdless boot failing and attempting to boot with initrd
[Regression Potential]
* This change adds a few more user visible message, without translations. The actual behaviour that is happening is unchanged. This simply better notifies users about what is happening, and can be inspected interactively, statically, and from boot logs.
[Other Info]
* CPC requested these UX improvements, as there have been concerns that users are failing to discover why initrdless boot is happening; or failing; and how to effect it. |
|
| 2021-08-12 09:42:06 |
Julian Andres Klode |
description |
[Impact]
(sort of prerequisite of bug 1929860 to avoid having to edit the patches and possibly introduce bugs that way)
* Sometimes it is not obvious why initrdless boot is generated; when is it attempted; and when it fails and boots with initrd.
* Improve UX by leaving breadcrumbs and emit messages about initrdless boot, in more places
[Test Case]
* Boot system with initrdless boot
- for example minimal cloud image from https://cloud-images.ubuntu.com/minimal/releases/
- boot without graphical terminal, i.e. -nographics qemu option
* Upgrade to new grub package
* Uncomment GRUB_TERMINAL=console in /etc/default/grub
1. Call `sudo update-grub`, a message should be emitted that initrdless boot will be attempted.
2. Inspecting /boot/grub/grub.cfg, there are comments that initrdless boot will be attempted
* Reboot
* Observe the following:
3. Inspecting console log, there are echo message from grub about attempting initrdless boot.
* Install linux-generic kernel flavour; and remove kvm kernel flavour, reboot.
* Observe in the console log
1. There should be message about attempting initrdless boot
2. kernel panic
3. message about initrdless boot failing and attempting to boot with initrd
[Regression Potential]
* This change adds a few more user visible message, without translations. The actual behaviour that is happening is unchanged. This simply better notifies users about what is happening, and can be inspected interactively, statically, and from boot logs.
[Other Info]
* CPC requested these UX improvements, as there have been concerns that users are failing to discover why initrdless boot is happening; or failing; and how to effect it. |
[Impact]
(sort of prerequisite of bug 1929860 to avoid having to edit the patches and possibly introduce bugs that way, because these changes port the service to systemd unit)
* Sometimes it is not obvious why initrdless boot is generated; when is it attempted; and when it fails and boots with initrd.
* Improve UX by leaving breadcrumbs and emit messages about initrdless boot, in more places
[Test Case]
* Boot system with initrdless boot
- for example minimal cloud image from https://cloud-images.ubuntu.com/minimal/releases/
- boot without graphical terminal, i.e. -nographics qemu option
* Upgrade to new grub package
* Uncomment GRUB_TERMINAL=console in /etc/default/grub
1. Call `sudo update-grub`, a message should be emitted that initrdless boot will be attempted.
2. Inspecting /boot/grub/grub.cfg, there are comments that initrdless boot will be attempted
* Reboot
* Observe the following:
3. Inspecting console log, there are echo message from grub about attempting initrdless boot.
* Install linux-generic kernel flavour; and remove kvm kernel flavour, reboot.
* Observe in the console log
1. There should be message about attempting initrdless boot
2. kernel panic
3. message about initrdless boot failing and attempting to boot with initrd
[Regression Potential]
* This change adds a few more user visible message, without translations. The actual behaviour that is happening is unchanged. This simply better notifies users about what is happening, and can be inspected interactively, statically, and from boot logs.
[Other Info]
* CPC requested these UX improvements, as there have been concerns that users are failing to discover why initrdless boot is happening; or failing; and how to effect it. |
|
| 2021-08-13 10:27:01 |
Łukasz Zemczak |
grub2 (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2021-08-13 10:27:03 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-08-13 10:27:05 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2021-08-13 10:27:08 |
Łukasz Zemczak |
tags |
|
verification-needed verification-needed-focal |
|
| 2021-08-19 08:44:14 |
Julian Andres Klode |
tags |
verification-needed verification-needed-focal |
verification-done verification-done-focal |
|
| 2021-08-19 08:51:22 |
Launchpad Janitor |
grub2 (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-08-19 08:51:29 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2021-09-29 10:51:59 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~juliank/grub/+git/bionic/+merge/409351 |
|
| 2021-09-29 10:54:24 |
Launchpad Janitor |
merge proposal unlinked |
https://code.launchpad.net/~juliank/grub/+git/bionic/+merge/409351 |
|
|
| 2021-09-29 10:55:07 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~juliank/grub/+git/bionic/+merge/409352 |
|
| 2021-10-08 10:48:43 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~beidl/grub/+git/ubuntu/+merge/409919 |
|
| 2021-10-14 13:55:21 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Bionic |
|
| 2021-10-14 13:55:21 |
Julian Andres Klode |
bug task added |
|
grub2 (Ubuntu Bionic) |
|
| 2021-10-14 13:55:27 |
Julian Andres Klode |
grub2 (Ubuntu Bionic): status |
New |
In Progress |
|
| 2021-11-29 13:05:12 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/412515 |
|
| 2021-11-30 18:37:13 |
Launchpad Janitor |
merge proposal unlinked |
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/412515 |
|
|
| 2021-12-01 18:25:45 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/412515 |
|
