Bug 1716164

Summary: Duplicated BOOT_IMAGE= kernel parameter
Product: [Fedora] Fedora Reporter: rvcsaba
Component: systemdAssignee: Peter Jones <pjones>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: fmartine, goeran, lnykryn, madko, msekleta, pjones, ssahani, s, systemd-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: systemd-243.8-1.fc31 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-02 09:55:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
some text file none

Description rvcsaba 2019-06-02 13:56:18 UTC 
Description of problem:

cat /proc/cmdline

BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.1.6-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.1.5-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.1.4-301.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.1.4-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.1.3-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.1.2-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.1.1-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.1.0-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.0.13-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.0.12-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.0.11-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.0.10-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.0.9-301.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.0.9-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.0.8-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.0.7-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.0.6-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/828e3dda913c46b59a25bf22fca6541b/5.0.5-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.0.0-300.fc30.x86_64 root=UUID=2b095fa7-c74f-4cd4-b731-06b36ea1b266 ro rd.lvm.lv=vg_deer/LogVol00 rd.md=0 rd.dm=0 rd.luks=0 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8 zswap.zpool=zsmalloc zswap.enabled=1 elevator=deadline acpi_enforce_resources=lax resume=UUID=1d73d41b-a0ed-408f-8b46-66230defe7ba

Version-Release number of selected component (if applicable):

rpm -qa grub2\* grubby\* | sort

grub2-common-2.02-81.fc30.noarch
grub2-pc-2.02-81.fc30.x86_64
grub2-pc-modules-2.02-81.fc30.noarch
grub2-starfield-theme-2.02-0.42.fc26.x86_64
grub2-tools-2.02-81.fc30.x86_64
grub2-tools-efi-2.02-81.fc30.x86_64
grub2-tools-extra-2.02-81.fc30.x86_64
grub2-tools-minimal-2.02-81.fc30.x86_64
grubby-8.40-30.fc30.x86_64


How reproducible:


Steps to Reproduce:

Actual results:


Expected results:


Additional info:
Comment 1 Javier Martinez Canillas 2019-08-06 20:45:14 UTC 
Could you please share the content of your /boot/grub2/grubenv, /etc/grub2.cfg and BLS files in /boot/loader/entries ?
Comment 2 rvcsaba 2019-08-07 21:24:15 UTC 
Created attachment 1601594 [details]
some text file

Why missing actual kernel version number in grub menu?
Comment 3 Javier Martinez Canillas 2019-08-07 21:38:47 UTC 
(In reply to rvcsaba from comment #2)
> Created attachment 1601594 [details]
> some text file
> 
> Why missing actual kernel version number in grub menu?

It seems the BLS snippet you have is not the one generated by /usr/lib/kernel/install.d/20-grub.install but instead by /usr/lib/kernel/install.d/90-loaderentry.install. The later generates BLS snippets that are meant to be used by systemd-boot and not grub2.

Do you have sd-boot installed? Also do you have a /boot/efi/828e3dda913c46b59a25bf22fca6541b directory?
Comment 4 rvcsaba 2019-08-08 20:29:42 UTC 
(In reply to Javier Martinez Canillas from comment #3)
> Do you have sd-boot installed?

Is this an exact package name? I not found it in repo. But:

rpm -qf /usr/lib/kernel/install.d/20-grub.install 
grub2-common-2.02-81.fc30.noarch

rpm -qf /usr/lib/kernel/install.d/20-grubby.install 
systemd-udev-241-10.git511646b.fc30.x86_64

rpm -qf /usr/lib/kernel/install.d/90-loaderentry.install 
systemd-udev-241-10.git511646b.fc30.x86_64



> Also do you have a /boot/efi/828e3dda913c46b59a25bf22fca6541b directory?

No.

pwd
/boot

tree efi/
efi/
└── EFI
    ├── BOOT
    └── fedora

3 directories, 0 files

What can I do?
Comment 5 Edouard Bourguignon 2019-08-24 08:12:03 UTC 
Same problem here. Is there a fix ?

No kernel version are shown in grub menu. And BOOT_IMAGE is wrong, containing all the kernel installed:

cat /proc/cmdline
BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.2.9-200.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.2.8-200.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.2.7-200.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.2.6-200.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.2.5-200.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.1.20-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.1.19-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.1.18-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.1.17-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.1.16-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.1.15-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.1.12-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.1.11-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.1.8-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.1.7-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.1.6-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.1.5-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.1.4-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.0.17-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.0.16-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.0.14-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.0.13-300.fc30.x86_64/linux BOOT_IMAGE=(hd0,gpt5)/5a68123777134e458e146023b9704f82/5.0.11-300.fc30.x86_64/linux BOOT_IMAGE=/vmlinuz-5.0.10-300.fc30.x86_64 root=/dev/mapper/taran-root ro resume=/dev/mapper/taran-swap rd.lvm.lv=taran/root

I don't have a /boot/efi/MACHINE_ID but I do have a /boot/MACHINE_ID

tree /boot/5a68123777134e458e146023b9704f82/
/boot/5a68123777134e458e146023b9704f82/
├── 0-rescue
│   ├── initrd
│   └── linux
├── 5.2.6-200.fc30.x86_64
│   ├── initrd
│   └── linux
├── 5.2.7-200.fc30.x86_64
│   ├── initrd
│   └── linux
├── 5.2.8-200.fc30.x86_64
│   ├── initrd
│   └── linux
└── 5.2.9-200.fc30.x86_64
    ├── initrd
    └── linux

5 directories, 10 files
Comment 6 rvcsaba 2019-12-03 22:10:54 UTC 
/usr/lib/kernel/install.d/90-loaderentry.install file is correct (systemd-udev-243.4-1.fc31.x86_64)?

From line 48:

if [[ -f /etc/kernel/cmdline ]]; then
    read -r -d '' -a BOOT_OPTIONS < /etc/kernel/cmdline
elif [[ -f /usr/lib/kernel/cmdline ]]; then
    read -r -d '' -a BOOT_OPTIONS < /usr/lib/kernel/cmdline
else
    declare -a BOOT_OPTIONS

    read -r -d '' -a line < /proc/cmdline
    for i in "${line[@]}"; do
        [[ "${i#initrd=*}" != "$i" ]] && continue
        BOOT_OPTIONS+=("$i")
    done
fi

/etc/kernel/cmdline and /usr/lib/kernel/cmdline missing. BOOT_OPTIONS generated from actually kernel parameters, including BOOT_IMAGE=.../5.3.14-300.fc31.x86_64/linux. Why not drop BOOT_IMAGE= parameter, or changed a value to new directory name (new kernel release name)?
Comment 7 Zbigniew Jędrzejewski-Szmek 2020-02-26 22:36:05 UTC 
https://github.com/systemd/systemd/pull/14950
Comment 8 Fedora Update System 2020-03-18 21:18:35 UTC 
FEDORA-2020-645de57f2e has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-645de57f2e
Comment 9 Fedora Update System 2020-03-19 02:26:37 UTC 
systemd-245.2-1.fc32 has been pushed to the Fedora 32 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-645de57f2e
Comment 10 Fedora Update System 2020-03-23 20:24:45 UTC 
FEDORA-2020-645de57f2e has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 11 Fedora Update System 2020-03-27 19:12:17 UTC 
FEDORA-2020-287a343a35 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-287a343a35`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-287a343a35

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 12 Fedora Update System 2020-04-02 09:55:21 UTC 
FEDORA-2020-287a343a35 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.