[Bug 1037206] New: 'Unrecognized option --no-nvram' during installation of mokutil package
http://bugzilla.suse.com/show_bug.cgi?id=1037206 Bug ID: 1037206 Summary: 'Unrecognized option --no-nvram' during installation of mokutil package Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: mnowak@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- `yast bootloader` asks to install additional packages and when it's doing it, it fails with: 'Unrecognized option --no-nvram'. https://openqa.opensuse.org/tests/396373#step/yast2_bootloader/7 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1037206 Chenzi Cao <chcao@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |glin@suse.com Assignee|bnc-team-screening@forge.pr |snwint@suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1037206 http://bugzilla.suse.com/show_bug.cgi?id=1037206#c1 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|snwint@suse.com |glin@suse.com --- Comment #1 from Steffen Winterfeldt <snwint@suse.com> --- cf bug 1031351 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1037206 http://bugzilla.suse.com/show_bug.cgi?id=1037206#c2 --- Comment #2 from Gary Ching-Pang Lin <glin@suse.com> --- Hmmm, according to shim.changes, "--no-nvram" was added since last December. I have to download the iso and have a close scrutiny. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1037206 http://bugzilla.suse.com/show_bug.cgi?id=1037206#c3 --- Comment #3 from Gary Ching-Pang Lin <glin@suse.com> --- I downloaded openSUSE-Leap-42.3-DVD-x86_64-Build0229-Media.iso and installed it in a VM. Nothing happened when installing mokutil and kexec-tools (I removed them manually and triggered the installation with yast-bootloader.) Will try the JeOS image later. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1037206 http://bugzilla.suse.com/show_bug.cgi?id=1037206#c4 Gary Ching-Pang Lin <glin@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@suse.com Assignee|glin@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com Flags| |needinfo?(jreidinger@suse.c | |om) --- Comment #4 from Gary Ching-Pang Lin <glin@suse.com> --- I found that the openQA VM was using SeaBIOS rather than OVMF, i.e. the VM was not running on UEFI. So, this issue is nothing to do with mokutil. It's using the UEFI bootloader config on a legacy BIOS machine, and this is totally wrong. Josef, Could you help to check the bootloader config? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1037206 Michal Nowak <mnowak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mnowak@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1037206 http://bugzilla.suse.com/show_bug.cgi?id=1037206#c5 Michal Nowak <mnowak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mchang@suse.com Flags| |needinfo?(mchang@suse.com) --- Comment #5 from Michal Nowak <mnowak@suse.com> --- (In reply to Gary Ching-Pang Lin from comment #4)
I found that the openQA VM was using SeaBIOS rather than OVMF, i.e. the VM was not running on UEFI. So, this issue is nothing to do with mokutil. It's using the UEFI bootloader config on a legacy BIOS machine, and this is totally wrong.
Josef, Could you help to check the bootloader config?
Michael Chang: Perhaps you can help with explaining, why we have "GRUB for EFI" on JeOS KVM image despite VM may not have UEFI? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1037206 http://bugzilla.suse.com/show_bug.cgi?id=1037206#c6 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gmoro@suse.com Flags|needinfo?(mchang@suse.com) |needinfo?(gmoro@suse.com) --- Comment #6 from Michael Chang <mchang@suse.com> --- (In reply to Michal Nowak from comment #5)
(In reply to Gary Ching-Pang Lin from comment #4)
Michael Chang: Perhaps you can help with explaining, why we have "GRUB for EFI" on JeOS KVM image despite VM may not have UEFI?
Not really .. But my speculation is kiwi first boot scripts did not setup /etc/sysconfig/bootloader correctly wrt firmware type being booted. If you use guestfish to inspect the qcow2 image https://openqa.opensuse.org/tests/396373/asset/hdd/openSUSE-Leap-42.3-JeOS-f... The /etc/sysconfig/bootloader is initially an empty file poised to be written. After the first boot, /etc/sysconfig/bootloader is filled with content below, which looks wrong as its being booted on legacy bios.
LOADER_TYPE="grub2-efi" LOADER_LOCATION="mbr" DEFAULT_APPEND=" root=/dev/disk/by-label/ROOT disk=/dev/sda resume=swap systemd.show_status=0 plymouth.enable=0 quiet" FAILSAFE_APPEND="ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processsor.max+cstate=1 nomodeset x11failsafe root=/dev/disk/by-label/ROOT disk=/dev/sda resume=swap systemd.show_status=0 plymouth.enable=0 quiet"
@Guilherme, What do you think ? Thanks, Michael -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1037206 http://bugzilla.suse.com/show_bug.cgi?id=1037206#c7 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jreidinger@suse.c | |om) | --- Comment #7 from Josef Reidinger <jreidinger@suse.com> --- agreed, yast2 bootloader require from installed system to have written /etc/sysconfig/bootloader and it respect what is written there. So if there is grub2-efi it will use it. If you provide logs, I can check if that is read from it or proposed if missing, but in general bootloader expect to have written correct bootloader there. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1037206 http://bugzilla.suse.com/show_bug.cgi?id=1037206#c9 Guilherme Moro <gmoro@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #9 from Guilherme Moro <gmoro@suse.com> --- Closing this, if it is reproducible in Leap 15 series please reopen. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com