Bug 1458770 - When using btrfs with EFI booted system, grub.cfg needs to be on /boot rather than /boot/efi/EFI/fedora
Summary: When using btrfs with EFI booted system, grub.cfg needs to be on /boot rather...
Keywords:
Status: CLOSED ERRATA
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: 1039124
TreeView+ depends on / blocked
 
Reported: 2017-06-05 12:25 UTC by Neal Gompa
Modified: 2019-02-19 23:39 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-02-19 23:39:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Neal Gompa 2017-06-05 12:25:46 UTC
Description of problem:
In order for boot-to-snapshot to be effective such that the boot configuration is snapshotted with the rest of the system, grub.cfg needs to be stored in the /boot btrfs subvolume rather than in the EFI system partition vendor folder (/boot/efi/EFI/fedora).

A symlink in the vendor folder back to the location in the btrfs /boot subvolume is fine.

This approach is used in openSUSE to ensure that the grub configuration is snapshotted with the rest of the system.

Version-Release number of selected component (if applicable):
2.02-0.38.fc26

Comment 1 Jan Kurik 2017-08-15 09:34:31 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 2 Ben Cotton 2018-11-27 18:28:39 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2019-02-19 17:12:07 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle.
Changing version to '30.

Comment 4 Chris Murphy 2019-02-19 23:39:24 UTC
In effect this is what the F30 bootloaderspec feature achieves. A static grub.cfg will still be on /boot/EFI/efi/fedora but updated menu entry drop-in scripts will be added to /boot/loader/entries per
https://fedoraproject.org/wiki/Releases/30/ChangeSet#Make_BootLoaderSpec-style_configuration_files_the_default


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