[Bug 1162320] New: grub2-arm64-efi upgrade 2.02-lp151.21.6.1 -> 2.02-lp151.21.9.1 causes system to fail reboot with "error: symbol `grub_efi_allocate_any_pages' not found."
http://bugzilla.opensuse.org/show_bug.cgi?id=1162320 Bug ID: 1162320 Summary: grub2-arm64-efi upgrade 2.02-lp151.21.6.1 -> 2.02-lp151.21.9.1 causes system to fail reboot with "error: symbol `grub_efi_allocate_any_pages' not found." Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: mchang@suse.com Reporter: okurz@suse.com QA Contact: jsrain@suse.com CC: arvidjaar@gmail.com, rw@suse.com Found By: --- Blocker: --- ## Observation On the machine "aarch64" within the openqa.opensuse.org system, which is a transactional system, the system failed to boot after a nightly system upgrade on 2020-01-14. I could pinpoint that the upgrade of grub2-arm64-efi 2.02-lp151.21.6.1 -> 2.02-lp151.21.9.1 triggers error: symbol `grub_efi_allocate_any_pages' not found. when trying to load the kernel and initrd image after grub. See https://progress.opensuse.org/issues/62102 for details where I originally recorded the problem. ## Workaround So far I did `zypper al grub2-arm64-efi`. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162320 http://bugzilla.opensuse.org/show_bug.cgi?id=1162320#c1 --- Comment #1 from Michael Chang <mchang@suse.com> --- Hi Oliver Would you please check /boot/grub2/arm64-efi is btrfs subvolume ? You can also refer to bug 1122591, comment 2 for more details. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162320 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |okurz@suse.com Flags| |needinfo?(okurz@suse.com) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162320 http://bugzilla.opensuse.org/show_bug.cgi?id=1162320#c2 Oliver Kurz <okurz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(okurz@suse.com) | --- Comment #2 from Oliver Kurz <okurz@suse.com> --- No, it's vfat: ``` /dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) ``` So I guess I can apply the same workaround as mentioned in https://bugzilla.opensuse.org/show_bug.cgi?id=1122591#c28 though no real fix is available yet. Thanks so far. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162320 http://bugzilla.opensuse.org/show_bug.cgi?id=1162320#c3 --- Comment #3 from Oliver Kurz <okurz@suse.com> --- @mchang may I ask, what are your plans regarding a fix? What ETA should I expect? days/weeks/months/years? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162320 http://bugzilla.opensuse.org/show_bug.cgi?id=1162320#c4 --- Comment #4 from Michael Chang <mchang@suse.com> --- (In reply to Oliver Kurz from comment #3)
@mchang may I ask, what are your plans regarding a fix? What ETA should I expect? days/weeks/months/years?
Hi Oliver, No, it is not grub. The installer is in charge of setting up the subvolumes. There seems to be no subvolumes proposed for the system initially. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162320 http://bugzilla.opensuse.org/show_bug.cgi?id=1162320#c5 --- Comment #5 from Michael Chang <mchang@suse.com> --- Please see bug 1122591, comment 6 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162320 http://bugzilla.opensuse.org/show_bug.cgi?id=1162320#c6 --- Comment #6 from Michael Chang <mchang@suse.com> --- Admittedly I am not much into openQA, but sourcing from bsc#1097235 claimed that the problem has been fixed, why openQA still (constantly) notify the failure result ? Is there anything from the test case has to check for a more close result ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162320 http://bugzilla.opensuse.org/show_bug.cgi?id=1162320#c7 --- Comment #7 from Oliver Kurz <okurz@suse.com> --- If you really think https://bugzilla.opensuse.org/show_bug.cgi?id=1122591#c6 is the right solution which I would find very bad as users can unknowingly run into unbootable systems then please at least update this and other other bug accordingly to communicate this intention. This bug here is still in "NEW" and you are the bug assignee but I guess it should be in "CONFIRMED" or "IN_PROGRESS" with an update on the actual plan, right? Or even set it to "RESOLVED" with the according resolution, e.g. pointing to the release notes that cover this for Leap and other distributions. I just checked again on the machine "aarch64" and just upgrading the package grub2-arm64-efi still breaks the boot with the same error as originally reported. Please keep in mind that this bug here is about an upgrade on a physical machine, so neither "migration" between different versions of products nor an openQA test itself. Also, the workaround as mentioned in https://bugzilla.opensuse.org/show_bug.cgi?id=1122591#c28 did not work for me. I assume that the instructions are incomplete, e.g. if the btrfs subvolume needs to be mounted or so. There is also an unanswered question about this in https://bugzilla.opensuse.org/show_bug.cgi?id=1122591#c34
Admittedly I am not much into openQA, but sourcing from bsc#1097235 claimed that the problem has been fixed, why openQA still (constantly) notify the failure result ? Is there anything from the test case has to check for a more close result ?
Regarding openQA test failure reminders, as https://bugzilla.opensuse.org/show_bug.cgi?id=1122591#c49 states:
This bug is still referenced in a failing openQA test: migration_media+scc_sle15_ha_alpha_node01 https://openqa.suse.de/tests/3886491
To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed
https://openqa.suse.de/tests/3886491#step/patch_sle/106 is the location in test results which seems to record the soft failure which comes from https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/2e020725b709... after checking that the necessary btrfs subvolume is not already there. So I consider the products still affected because either the bugfix is not effective or never reached the affected product(s). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162320 http://bugzilla.opensuse.org/show_bug.cgi?id=1162320#c59 --- Comment #59 from OBSbugzilla Bot <bwiedemann+obsbugzillabot@suse.com> --- This is an autogenerated message for OBS integration: This bug (1162320) was mentioned in https://build.opensuse.org/request/show/930877 15.2 / transactional-update -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com