| 2015-04-14 02:13:01 |
Robie Basak |
bug |
|
|
added bug |
| 2015-04-14 02:14:50 |
Robie Basak |
description |
Steps to reproduce:
1. Boot a Vivid system installed from the server installer (not a cloud image).
2. Kill the power (or VM) while the kernel is initialising but before it has started init.
3. Power up the system (or start the VM) again.
Expected behaviour: the system should boot without user intervention.
Actual behaviour: the system hangs on the grub prompt.
This was previously raised in bug 669481 but the solution applied then was just to add the RECORDFAIL_TIMEOUT setting defaulted to -1. This allowed users to work around the problem by tuning RECORDFAIL_TIMEOUT. I'm filing this bug separately as there is nothing wrong with the previous fix, but it didn't fix the problem for users by default. This bug is about fixing the default so that users don't have to discover and work around the issue.
An IRC discussion (http://irclogs.ubuntu.com/2015/02/27/%23ubuntu-devel.html#t13:54) concluded that everyone involved in the discussion is happy to change the timeout from infinity to 30s.
Colin asked for a fix in Debian, so I'll send a patch there and add a bug link. I'm also filing the bug here in order to track the fix in both Debian and Ubuntu.
Importance: High because of the impact to users on headless servers - from their perspective, this causes a system to fail to boot after an appropriately timed double power cut. I'm prompted to do this today because it just happened to me on my server, so perhaps it's more likely than I originally thought. |
Steps to reproduce:
1. Boot a Vivid system installed from the server installer (not a cloud image).
2. Kill the power (or VM) while the kernel is initialising but before it has started init.
3. Power up the system (or start the VM) again.
Expected behaviour: the system should boot without user intervention.
Actual behaviour: the system hangs on the grub prompt.
This was previously raised in bug 669481 but the solution applied then was just to add the GRUB_RECORDFAIL_TIMEOUT setting defaulted to -1. This allowed users to work around the problem by tuning GRUB_RECORDFAIL_TIMEOUT. I'm filing this bug separately as there is nothing wrong with the previous fix, but it didn't fix the problem for users by default. This bug is about fixing the default so that users don't have to discover and work around the issue.
An IRC discussion (http://irclogs.ubuntu.com/2015/02/27/%23ubuntu-devel.html#t13:54) concluded that everyone involved in the discussion is happy to change the timeout from infinity to 30s.
Colin asked for a fix in Debian, so I'll send a patch there and add a bug link. I'm also filing the bug here in order to track the fix in both Debian and Ubuntu.
Importance: High because of the impact to users on headless servers - from their perspective, this causes a system to fail to boot after an appropriately timed double power cut. I'm prompted to do this today because it just happened to me on my server, so perhaps it's more likely than I originally thought. |
|
| 2015-04-14 02:34:59 |
Robie Basak |
summary |
recordfail false positive causes headless servers to hang on boot |
recordfail false positive causes headless servers to hang on boot by default |
|
| 2015-04-14 02:36:21 |
Robie Basak |
bug watch added |
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782552 |
|
| 2015-04-14 02:36:21 |
Robie Basak |
bug task added |
|
grub2 (Debian) |
|
| 2015-04-14 03:56:53 |
Bug Watch Updater |
grub2 (Debian): status |
Unknown |
New |
|
| 2015-04-14 07:22:01 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto Murata |
| 2015-05-15 15:53:40 |
Bug Watch Updater |
grub2 (Debian): status |
New |
Fix Released |
|
| 2015-05-19 08:59:17 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Server Team |
| 2015-05-19 13:23:07 |
Robie Basak |
nominated for series |
|
Ubuntu Trusty |
|
| 2015-05-19 13:23:07 |
Robie Basak |
bug task added |
|
grub2 (Ubuntu Trusty) |
|
| 2015-05-19 13:23:07 |
Robie Basak |
nominated for series |
|
Ubuntu Vivid |
|
| 2015-05-19 13:23:07 |
Robie Basak |
bug task added |
|
grub2 (Ubuntu Vivid) |
|
| 2015-05-19 13:23:07 |
Robie Basak |
nominated for series |
|
Ubuntu Precise |
|
| 2015-05-19 13:23:07 |
Robie Basak |
bug task added |
|
grub2 (Ubuntu Precise) |
|
| 2015-05-19 13:23:07 |
Robie Basak |
nominated for series |
|
Ubuntu Utopic |
|
| 2015-05-19 13:23:07 |
Robie Basak |
bug task added |
|
grub2 (Ubuntu Utopic) |
|
| 2015-05-19 13:23:16 |
Robie Basak |
grub2 (Ubuntu Precise): status |
New |
Triaged |
|
| 2015-05-19 13:23:19 |
Robie Basak |
grub2 (Ubuntu Trusty): status |
New |
Triaged |
|
| 2015-05-19 13:23:21 |
Robie Basak |
grub2 (Ubuntu Utopic): status |
New |
Triaged |
|
| 2015-05-19 13:23:24 |
Robie Basak |
grub2 (Ubuntu Vivid): status |
New |
Triaged |
|
| 2015-05-19 13:23:27 |
Robie Basak |
grub2 (Ubuntu Precise): importance |
Undecided |
High |
|
| 2015-05-19 13:23:29 |
Robie Basak |
grub2 (Ubuntu Trusty): importance |
Undecided |
High |
|
| 2015-05-19 13:23:32 |
Robie Basak |
grub2 (Ubuntu Utopic): importance |
Undecided |
High |
|
| 2015-05-19 13:23:34 |
Robie Basak |
grub2 (Ubuntu Vivid): importance |
Undecided |
High |
|
| 2015-05-19 13:29:12 |
Robie Basak |
description |
Steps to reproduce:
1. Boot a Vivid system installed from the server installer (not a cloud image).
2. Kill the power (or VM) while the kernel is initialising but before it has started init.
3. Power up the system (or start the VM) again.
Expected behaviour: the system should boot without user intervention.
Actual behaviour: the system hangs on the grub prompt.
This was previously raised in bug 669481 but the solution applied then was just to add the GRUB_RECORDFAIL_TIMEOUT setting defaulted to -1. This allowed users to work around the problem by tuning GRUB_RECORDFAIL_TIMEOUT. I'm filing this bug separately as there is nothing wrong with the previous fix, but it didn't fix the problem for users by default. This bug is about fixing the default so that users don't have to discover and work around the issue.
An IRC discussion (http://irclogs.ubuntu.com/2015/02/27/%23ubuntu-devel.html#t13:54) concluded that everyone involved in the discussion is happy to change the timeout from infinity to 30s.
Colin asked for a fix in Debian, so I'll send a patch there and add a bug link. I'm also filing the bug here in order to track the fix in both Debian and Ubuntu.
Importance: High because of the impact to users on headless servers - from their perspective, this causes a system to fail to boot after an appropriately timed double power cut. I'm prompted to do this today because it just happened to me on my server, so perhaps it's more likely than I originally thought. |
[Impact]
On a headless server system, a user who does not have easy access to the console may find the system fails to come up after a power cut because the boot is blocked on a console menu prompt from grub that does not time out.
[Workaround]
Set GRUB_RECORDFAIL_TIMEOUT to some positive value (eg. 30) in /etc/default/grub and then run "sudo update-grub". However this needs to have been done before the problem occurs; when it has occurred, the only option a user has is to add a head to a headless system.
[Development Fix]
Default for GRUB_RECORDFAIL_TIMEOUT changed from -1 (indefinite wait) to 30 (proceed anyway after 30 seconds). Accepted in Debian, synced to Ubuntu in Wily; currently held in wily-proposed due to some items in the unapproved queue.
[Stable Fix]
Same as development fix.
[Regression Potential]
This fix changes user-visible behaviour deliberately because the previous behaviour led to this bug. Users of non-headless systems (eg. desktop) may miss the boot menu and come back to a failed boot or something; but if they attempt again, they should see the menu prompt for 30 seconds anyway.
[Test Case]
Steps to reproduce:
1. Boot a Vivid system installed from the server installer (not a cloud image).
2. Kill the power (or VM) while the kernel is initialising but before it has started init.
3. Power up the system (or start the VM) again.
Expected behaviour: the system should boot without user intervention.
Actual behaviour: the system hangs on the grub prompt.
[Details]
This was previously raised in bug 669481 but the solution applied then was just to add the GRUB_RECORDFAIL_TIMEOUT setting defaulted to -1. This allowed users to work around the problem by tuning GRUB_RECORDFAIL_TIMEOUT. I'm filing this bug separately as there is nothing wrong with the previous fix, but it didn't fix the problem for users by default. This bug is about fixing the default so that users don't have to discover and work around the issue.
An IRC discussion (http://irclogs.ubuntu.com/2015/02/27/%23ubuntu-devel.html#t13:54) concluded that everyone involved in the discussion is happy to change the timeout from infinity to 30s.
Colin asked for a fix in Debian, so I'll send a patch there and add a bug link. I'm also filing the bug here in order to track the fix in both Debian and Ubuntu.
Importance: High because of the impact to users on headless servers - from their perspective, this causes a system to fail to boot after an appropriately timed double power cut. I'm prompted to do this today because it just happened to me on my server, so perhaps it's more likely than I originally thought. |
|
| 2015-05-19 14:04:15 |
Robie Basak |
attachment added |
|
trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1443735/+attachment/4400229/+files/trusty.debdiff |
|
| 2015-05-19 14:04:30 |
Robie Basak |
attachment added |
|
utopic.debdiff https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1443735/+attachment/4400230/+files/utopic.debdiff |
|
| 2015-05-19 14:04:50 |
Robie Basak |
attachment added |
|
precise.debdiff https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1443735/+attachment/4400231/+files/precise.debdiff |
|
| 2015-05-19 14:05:07 |
Robie Basak |
attachment added |
|
vivid.debdiff https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1443735/+attachment/4400232/+files/vivid.debdiff |
|
| 2015-05-19 15:25:19 |
Diogo Matsubara |
bug |
|
|
added subscriber Diogo Matsubara |
| 2015-05-19 16:19:24 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2015-05-22 13:46:36 |
Launchpad Janitor |
grub2 (Ubuntu): status |
Triaged |
Fix Released |
|
| 2015-05-26 21:24:24 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/grub2 |
|
| 2015-05-27 04:41:51 |
Launchpad Janitor |
branch linked |
|
lp:debian/grub2 |
|
| 2015-05-27 04:41:54 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-branches/debian/stretch/grub2/stretch |
|
| 2015-06-26 09:43:27 |
Robie Basak |
grub2 (Ubuntu Precise): status |
Triaged |
In Progress |
|
| 2015-06-26 09:43:29 |
Robie Basak |
grub2 (Ubuntu Trusty): status |
Triaged |
In Progress |
|
| 2015-06-26 09:43:32 |
Robie Basak |
grub2 (Ubuntu Utopic): status |
Triaged |
In Progress |
|
| 2015-06-26 09:43:34 |
Robie Basak |
grub2 (Ubuntu Vivid): status |
Triaged |
In Progress |
|
| 2015-06-26 10:33:04 |
Timo Aaltonen |
grub2 (Ubuntu Vivid): status |
In Progress |
Fix Committed |
|
| 2015-06-26 10:33:06 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2015-06-26 10:33:10 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2015-06-26 10:33:16 |
Timo Aaltonen |
tags |
patch |
patch verification-needed |
|
| 2015-06-26 10:34:24 |
Timo Aaltonen |
grub2 (Ubuntu Utopic): status |
In Progress |
Fix Committed |
|
| 2015-06-26 10:35:43 |
Timo Aaltonen |
grub2 (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2015-06-26 10:43:46 |
Timo Aaltonen |
grub2 (Ubuntu Precise): status |
In Progress |
Fix Committed |
|
| 2015-06-26 10:49:43 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/vivid-proposed/grub2 |
|
| 2015-06-26 10:49:44 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/trusty-proposed/grub2 |
|
| 2015-06-26 10:49:47 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/utopic-proposed/grub2 |
|
| 2015-06-26 10:59:05 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/precise-proposed/grub2 |
|
| 2015-06-27 06:02:02 |
paz |
bug |
|
|
added subscriber paz |
| 2015-07-03 09:49:36 |
Robie Basak |
bug task added |
|
grub2-signed (Ubuntu) |
|
| 2015-07-03 10:31:17 |
Timo Aaltonen |
grub2-signed (Ubuntu Utopic): status |
New |
Fix Committed |
|
| 2015-07-03 10:32:43 |
Timo Aaltonen |
grub2-signed (Ubuntu Vivid): status |
New |
Fix Committed |
|
| 2015-07-03 11:03:39 |
Adam Conrad |
grub2-signed (Ubuntu): status |
New |
Fix Released |
|
| 2015-07-03 11:04:07 |
Adam Conrad |
grub2-signed (Ubuntu Precise): status |
New |
Fix Committed |
|
| 2015-07-03 11:04:51 |
Adam Conrad |
grub2-signed (Ubuntu Trusty): status |
New |
Fix Committed |
|
| 2015-07-03 11:07:54 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/precise-proposed/grub2-signed |
|
| 2015-07-03 11:07:55 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/trusty-proposed/grub2-signed |
|
| 2015-07-04 02:11:19 |
Diogo Matsubara |
tags |
patch verification-needed |
patch verification-done |
|
| 2015-07-08 04:17:46 |
Launchpad Janitor |
grub2 (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2015-07-08 04:17:52 |
Scott Kitterman |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2015-07-08 04:29:15 |
Launchpad Janitor |
grub2 (Ubuntu Vivid): status |
Fix Committed |
Fix Released |
|
| 2015-07-08 04:29:31 |
Launchpad Janitor |
grub2 (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
| 2015-07-08 04:50:12 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/precise-updates/grub2 |
|
| 2015-07-08 12:15:02 |
Launchpad Janitor |
grub2-signed (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
| 2015-07-08 12:15:26 |
Launchpad Janitor |
grub2-signed (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2015-07-08 12:15:34 |
Launchpad Janitor |
grub2-signed (Ubuntu Utopic): status |
Fix Committed |
Fix Released |
|
| 2015-07-08 12:15:42 |
Launchpad Janitor |
grub2-signed (Ubuntu Vivid): status |
Fix Committed |
Fix Released |
|
| 2015-07-08 12:18:05 |
Launchpad Janitor |
grub2 (Ubuntu Utopic): status |
Fix Committed |
Fix Released |
|
| 2015-07-17 09:34:05 |
Ewan |
bug |
|
|
added subscriber Ewan |
