cloud-sig

#441 cloud images are missing `saved_entry` in grubenv
Opened by martinpitt. Modified

Open
Close 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!

This should be fixed with future images:

  • Rawhide: https://pagure.io/fedora-kiwi-descriptions/c/c3e509d22eb177a1bbf99c4a1e73669048598bfc?branch=rawhide
  • F42: https://pagure.io/fedora-kiwi-descriptions/c/4059f135844892a087ef3e5cc15052467ea9e7fa?branch=f42

And we were accidentally not in BLS mode, which is fixed with updates to kiwi and setting a flag in the descriptions now:

  • Rawhide: https://pagure.io/fedora-kiwi-descriptions/c/15f8d0abf9097a2d5bc97f64da49b059f3e870f9?branch=f42
  • F42: https://pagure.io/fedora-kiwi-descriptions/c/15f8d0abf9097a2d5bc97f64da49b059f3e870f9?branch=f42

Thanks @ngompa! Happy to test the images in a week or so.

Thank you @ngompa!
@martinpitt, please let us know in case something still isn't working the way you expect (:

Thanks @ngompa ! I'll happily test a new cloud image once I find one.

Does anyone happen to know where to get a current image? Both https://download.fedoraproject.org/pub/fedora/linux/releases/42/Cloud/x86_64/images/ and https://kojipkgs.fedoraproject.org/compose/42/latest-Fedora-42/compose/Cloud/x86_64/images/ have an ancient (well, in computer terms, over one month) image. Shouldn't these be built as part of composes, so that new deployments start with the latest security/bug fix updates?

They are present here: https://kojipkgs.fedoraproject.org/compose/cloud/latest-Fedora-Cloud-42/compose/Cloud/

Thanks! I tested Fedora-Cloud-Base-Generic-42-20250507.0.x86_64.qcow2 and there is still no saved_entry in grub:

# grub2-editenv - list
boot_success=0

and the grubby randomness still appears:

cp /boot/vmlinuz-6.14.5-300.fc42.x86_64{,_clone1}
cp /boot/initramfs-6.14.5-300.fc42.x86_64.img{,_clone1}
grubby --initrd=/boot/initramfs-6.14.5-300.fc42.x86_64.img_clone1 --add-kernel=/boot/vmlinuz-6.14.5-300.fc42.x86_64_clone1 --title=Clone1 --args=test=kernel --copy-default
grubby --default-title

The last command says "Clone1" (i.e. new kernel unexpectedly becomes the default) in about half of the boots.

Metadata Update from @davdunc:
- Issue tagged with: meeting

Keeping the meeting tag on this for additional investigation. discussed shortly in meeting on July 3, 2025
Edited by davdunc
Metadata
None

meeting

None
None
None
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.