[Bug 1910815] Autopkgtest regression report (grub2/2.04-1ubuntu35.4)
Ubuntu SRU Bot
1910815 at bugs.launchpad.net
Mon Feb 15 20:04:57 UTC 2021
All autopkgtests for the newly accepted grub2 (2.04-1ubuntu35.4) for groovy have finished running.
The following regressions have been reported in tests triggered by the package:
ubiquity/unknown (amd64)
grml2usb/unknown (amd64)
zsys/unknown (amd64)
grubzfs-testsuite/unknown (amd64)
ubuntu-image/unknown (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/groovy/update_excuses.html#grub2
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1910815
Title:
race on boot between multiple invocations of grub-editenv
Status in grub2 package in Ubuntu:
Fix Committed
Status in grub2 source package in Focal:
Fix Committed
Status in grub2 source package in Groovy:
Fix Committed
Status in grub2 source package in Hirsute:
Fix Committed
Bug description:
[Impact]
* two grub systemd units run in parallel.
* ensure they are serialzed.
[Test Case]
* boot on initrdless systems (such as modern/recent public cloud
instances)
* observe that grub-initrd-fallback.service is always after grub-
common.service
* observe that both are successful
this is easy to view using
$ sudo journalctl -u grub-initrd-fallback.service grub-common.service
the output should be in order, not interleaved, with grub-common first
and then grub-initrd-fallback.
[Where problems could occur]
* The boot is slightly slower as the two jobs are serialized, but
they are not computationally intensive and shouldn't affect bootspeed
at all, especially on multicore systems where other things are
happening in parallel to these.
[Other Info]
* Original bug report
On focal, it appears systemd can run /etc/init.d/grub-common in parallel with /lib/systemd/system/grub-initrd-fallback.service. Both of these invoke grub-editenv for different reasons, apparently resulting in race conditions that generate messages like this:
Jan 08 18:07:15 asr-host systemd[1]: Starting LSB: Record successful boot for GRUB...
Jan 08 18:07:15 asr-host systemd[1]: Starting GRUB failed boot detection...
[..]
Jan 08 18:07:15 asr-host grub-common[1822]: * Recording successful boot for GRUB
[..]
Jan 08 18:07:16 asr-host grub-editenv[1886]: /usr/bin/grub-editenv: error: cannot rename the file /boot/grub/grubenv.new to /boot/grub/grubenv.
Jan 08 18:07:16 asr-host systemd[1]: grub-initrd-fallback.service: Main process exited, code=exited, status=1/FAILURE
Jan 08 18:07:16 asr-host systemd[1]: grub-initrd-fallback.service: Failed with result 'exit-code'.
Jan 08 18:07:16 asr-host systemd[1]: Failed to start GRUB failed boot detection.
Jan 08 18:07:16 asr-host grub-common[1822]: ...done.
Jan 08 18:07:16 asr-host systemd[1]: Started LSB: Record successful boot for GRUB.
Google search for "Failed to start GRUB failed boot detection" throws
up a few hits, which suggests this isn't necessarily something to
weird about the machine I'm running on:
https://www.google.co.uk/search?q=%22Failed+to+start+GRUB+failed+boot+detection.%22
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: grub-common 2.04-1ubuntu26.7
ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
Uname: Linux 5.4.0-59-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Jan 8 20:19:42 2021
ProcEnviron:
TERM=screen.xterm-256color
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: grub2
UpgradeStatus: Upgraded to focal on 2020-12-23 (15 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1910815/+subscriptions
More information about the foundations-bugs
mailing list