coreos / coreos/bootupd

Static GRUB config migration does not handle GRUB configs stored in ESP

Open
#857 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/migration area/static-grub-configs
Dominant language
Rust
Stars
196
Forks
55
Avg merge
3d 2h
Merged PRs (30d)
14

Description

On older Silverblue systems (installed from Silverblue 33 at least), the GRUB config is stored in the ESP instead of /boot.

The migration logic that we have right now is not enough, as it would have to look at this file as well, clean it up, and enable blscfg and maybe also make sure to add the info pointing GRUB to the boot partition to find the boot entries.

See: https://discussion.fedoraproject.org/t/sb42-updates-fail-on-system-with-512mb-boot-128mb-boot-efi/145041/14

And also: https://github.com/coreos/bootupd/issues/856

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests; start by locating the existing static GRUB configuration migration and examining how it finds and updates configurations. Compare that logic with GRUB configurations stored in the ESP, then verify that migration cleans the ESP configuration, enables blscfg, and preserves the boot partition information needed to find boot entries.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.