fedora-infrastructure

#12542 cloud images are missing `saved_entry` in grubenv
Closed: Upstream by zlopez. Opened by martinpitt.

Closed: Upstream
Reopen Issue

I reported an unpredictable behaviour of grubby in Fedora 42 cloud images here: https://bugzilla.redhat.com/show_bug.cgi?id=2361624 @mlewando argued that this is a bug in the cloud image build instead: it ought to have a saved_entry in its grubenv file. The default images don't:

# grub2-editenv - list
boot_success=0

I confirm that running grubby --set-default-index 0 explicitly before some actually wanted grubby command works around the issue. But that is an "unbreak my setup" workaround. It should also not explicitly be in the cloud image build scripts for the same reason. Perhaps the cloud image build resets the grub config somehow?

@mlewando can you please describe in more detail what needs to happen during image build?

Thanks!

We don't do the image builds, we just host the pipeline for that. You should reach to Fedora Cloud SIG and open issue on their tracker.

Metadata Update from @zlopez:
- Issue close_status updated to: Upstream
- Issue status updated to: Closed (was: Open)

Ack, thanks @zlopez ! I didn't know where to report that. I filed https://pagure.io/cloud-sig/issue/441

Ack, thanks @zlopez ! I didn't know where to report that. I filed https://pagure.io/cloud-sig/issue/441
Metadata
None
None
None
None
Lowest
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.