Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1688453 - Fedora IoT(ostree) disk images have two identical boot menu entries
Summary: Fedora IoT(ostree) disk images have two identical boot menu entries
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: IoT
TreeView+ depends on / blocked
 
Reported: 2019-03-13 18:07 UTC by Paul Whalen
Modified: 2019-04-05 19:09 UTC (History)
3 users (show)

Fixed In Version: grub2-2.02-75.fc30
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-01 00:01:21 UTC


Attachments (Terms of Use)
from /boot/efi/EFI/fedora/grub.cfg (deleted)
2019-03-13 18:21 UTC, Paul Whalen
no flags Details
from /boot/loader/grub.cfg (deleted)
2019-03-13 18:22 UTC, Paul Whalen
no flags Details

Description Paul Whalen 2019-03-13 18:07:43 UTC
Description of problem:
Booting a recent Fedora IoT(ostree) disk image (Fedora-IoT-30-20190312.1.aarch64.raw.xz) there are two duplicate boot menu entries. This appears to be a result of having a grub.cfg and bls snippet. 

      Fedora 30 (IoT Edition) 30.20190312.1 (ostree)                                                                                                                                          
      Fedora 30 (IoT Edition) 30.20190312.1 (ostree)                                                                                                                                         
      System setup       

The first entry:

load_video                                                                                                                                                                                    
set gfx_payload=keep                                                                                                                                                                         
insmod gzio                                                                                                                                                                                  
linux ($root)/ostree/fedora-iot-6542e513f9f4574dc666f82314a6ab0357707892d3229d03fb147fe912378ac4/vmlinuz-5.0.0-300.fc30.aarch64 net.ifnames=0 modprobe.blacklist=vc4 root=UUID=040d735a-2828-4e4a-9ec8-c4304ead7712 ostree=/ostree/boot.0/fedora-iot/6542e513f9f4574dc666f82314a6ab0357707892d3229d03fb147fe912378ac4/0                                
initrd ($root)/ostree/fedora-iot-6542e513f9f4574dc666f82314a6ab0357707892d3229d03fb147fe912378ac4/initramfs-5.0.0-300.fc30.aarch64.img                                

Second:
setparams 'Fedora 30 (IoT Edition) 30.20190312.1 (ostree)' 'ostree-0-b45e4772-6204-4782-a9f1-b36a52895c40'                                                                                    
                                                                                                                                                                                             
load_video                                                                                                                                                                                   
set gfxpayload=keep                                                                                                                                                                          
insmod gzio                                                                                                                                                                                  
insmod part_msdos                                                                                                                                                                            
insmod ext2                                                                                                                                                                                  
if [ x$feature_platform_search_hint = xy ]; then                                                                                                                                             
  search --no-floppy --fs-uuid --set=root  b45e4772-6204-4782-a9f1-b36a52895c40                                                                                                              
else                                                                                                                                                                                         
  search --no-floppy --fs-uuid --set=root b45e4772-6204-4782-a9f1-b36a52895c40                                                                                                               
fi                                                                                                                                                                                           
linux /ostree/fedora-iot-6542e513f9f4574dc666f82314a6ab0357707892d3229d03fb147fe912378ac4/vmlinuz-5.0.0-300.fc30.aarch64 net.ifnames=0 modprobe.blacklist=vc4 root=UUID=040d735a-2828-4e4a-9\
ec8-c4304ead7712 ostree=/ostree/boot.0/fedora-iot/6542e513f9f4574dc666f82314a6ab0357707892d3229d03fb147fe912378ac4/0                                                                         
initrd /ostree/fedora-iot-6542e513f9f4574dc666f82314a6ab0357707892d3229d03fb147fe912378ac4/initramfs-5.0.0-300.fc30.aarch64.img                          

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

Listing all grub related packages 

grub2-tools-extra-2.02-72.fc30.aarch64
greenboot-ostree-grub2-0.6-1.fc30.noarch
grub2-tools-minimal-2.02-72.fc30.aarch64
greenboot-grub2-0.6-1.fc30.noarch
grub2-tools-2.02-72.fc30.aarch64
grub2-common-2.02-72.fc30.noarch
grub2-efi-aa64-2.02-72.fc30.aarch64
ostree-grub2-2019.1-5.fc30.aarch64

The disk images and logs can be found in koji - https://koji.fedoraproject.org/koji/taskinfo?taskID=33436420

Comment 1 Javier Martinez Canillas 2019-03-13 18:12:02 UTC
Hello Paul,

Can you please share your grub2.cfg.

Comment 2 Paul Whalen 2019-03-13 18:21:10 UTC
Created attachment 1543719 [details]
from /boot/efi/EFI/fedora/grub.cfg

Comment 3 Paul Whalen 2019-03-13 18:22:02 UTC
Created attachment 1543720 [details]
from /boot/loader/grub.cfg

Comment 4 Javier Martinez Canillas 2019-03-14 10:24:57 UTC
So the problem here is that both the 10_linux and 15_ostree grub.d plugins are executed, so there's a section that calls blscfg (which parses the BLS snippet in /boot/loader/entries) and another section that has a menu entry generated by ostree admin instutil grub2-generate command.

This is because the BLS configuration is enabled (GRUB_ENABLE_BLSCFG=true in /etc/default/grub), but Anaconda shouldn't do it for the Fedora IoT spin.

Comment 5 Fedora Update System 2019-03-29 16:45:08 UTC
grub2-2.02-75.fc30 systemd-241-4.gitcbf14c9.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-616045ca76

Comment 6 Fedora Update System 2019-03-29 20:32:36 UTC
grub2-2.02-75.fc30, systemd-241-4.gitcbf14c9.fc30 has been pushed to the Fedora 30 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-2019-616045ca76

Comment 7 Fedora Update System 2019-04-01 00:01:21 UTC
grub2-2.02-75.fc30, systemd-241-4.gitcbf14c9.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Paul Whalen 2019-04-05 19:09:08 UTC
This is still an issue in the latest f30 iot nightlies.


Note You need to log in before you can comment on or make changes to this bug.