Regression: bootc incorrectly detecting missing bootupd

[KKoukiou]

Since latest update [1] anaconda bootc tests started failing:

[1] https://bodhi.fedoraproject.org/updates/FEDORA-2025-a47496d227

The image contains the bootupd package: bootupd-0.2.31-1.fc44.x86_64

The version of bootc is: bootc-1.10.0-2.fc44.x86_64

12:21:03,312 WARNING org.fedoraproject.Anaconda.Modules.Payloads:DEBUG:anaconda.modules.payloads.payload.rpm_ostree.installation:bootc output: error: Installing to filesystem: bootupd is required for ostree-based installs 
...
3792 12:21:03,753 WARNING org.fedoraproject.Anaconda.Modules.Payloads:pyanaconda.modules.common.errors.installation.PayloadInstallationError: bootc installation failed: process '['bootc', 'i     nstall', 'to-filesystem', '--root-mount-spec=UUID=052a29d5-c8c2-4b29-b234-8bce4f7416d6', '--boot-mount-spec=UUID=ed888a3c-4980-4c0b-8571-5de28db84ccf', '--stateroot=test-stateroot', '--     source-imgref=registry:quay.io/fedora/fedora-bootc:rawhide', '--target-imgref=registry:quay.io/fedora/fedora-bootc:rawhide', '/mnt/sysimage', '--karg=rd.lvm.lv=fedora_ibm-p8-kvm-03-gues     t-02/root', '--karg=rd.luks.uuid=luks-bad313c7-65ea-42c1-9ca5-75b1d57e634f']' exited with status 1
3793 12:21:03,754 WARNING org.fedoraproject.Anaconda.Modules.Payloads:INFO:anaconda.core.threads:Thread Done: AnaTaskThread-DeployBootcTask-1 (139924088080064)
3794 12:21:03,847 WARNING org.fedoraproject.Anaconda.Modules.Payloads:WARNING:dasbus.server.handler:The call org.fedoraproject.Anaconda.Task.Finish has failed with an exception:
3795 12:21:03,847 WARNING org.fedoraproject.Anaconda.Modules.Payloads:Traceback (most recent call last):
3796 12:21:03,847 WARNING org.fedoraproject.Anaconda.Modules.Payloads:  File "/usr/lib64/python3.14/site-packages/pyanaconda/modules/payloads/payload/rpm_ostree/installation.py", line 875, i     n run
3797 12:21:03,847 WARNING org.fedoraproject.Anaconda.Modules.Payloads:    for line in execReadlines("bootc", bootc_args):
3798 12:21:03,847 WARNING org.fedoraproject.Anaconda.Modules.Payloads:                ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
3799 12:21:03,847 WARNING org.fedoraproject.Anaconda.Modules.Payloads:  File "/usr/lib64/python3.14/site-packages/pyanaconda/core/util.py", line 416, in __next__
3800 12:21:03,847 WARNING org.fedoraproject.Anaconda.Modules.Payloads:    raise OSError("process '%s' exited with status %s" %
3801 12:21:03,847 WARNING org.fedoraproject.Anaconda.Modules.Payloads:                  (self._argv, self._proc.returncode))
3802 12:21:03,847 WARNING org.fedoraproject.Anaconda.Modules.Payloads:OSError: process '['bootc', 'install', 'to-filesystem', '--root-mount-spec=UUID=052a29d5-c8c2-4b29-b234-8bce4f7416d6', '     --boot-mount-spec=UUID=ed888a3c-4980-4c0b-8571-5de28db84ccf', '--stateroot=test-stateroot', '--source-imgref=registry:quay.io/fedora/fedora-bootc:rawhide', '--target-imgref=registry:qua     y.io/fedora/fedora-bootc:rawhide', '/mnt/sysimage', '--karg=rd.lvm.lv=fedora_ibm-p8-kvm-03-guest-02/root', '--karg=rd.luks.uuid=luks-bad313c7-65ea-42c1-9ca5-75b1d57e634f']' exited with      status 1

[ckyrouac]

Could you try specifying --bootloader grub in the bootc install invocation here? https://github.com/rhinstaller/anaconda/blob/0fa1c7a2f271ba1ed5dd1456def57a7295efb5cc/pyanaconda/modules/payloads/payload/rpm_ostree/installation.py#L833

[cgwalters]

The root of the regression here is that when running bootc install outside of a container, we're looking in the host root, which we should not do.

I think in theory we might be able to defer bootloader handling until after we've fetched the target container image.

Also, in general we're going to need to extend our testing of bootc install outside a container.

Probably what would be most valuable is doing a full bootc-image-builder anaconda-iso flow here - at long as we're careful to override the bootc-installed-into-anaconda (as distinct from the target version).

[cgwalters]

I think in theory we might be able to defer bootloader handling until after we've fetched the target container image.

Well no because determining if we have a UKI also affects things like whether we use composefs etc.

We could try to move early detection of things like this to labels instead, but that would become a bit more of a burden on the build side.

In the more medium term I think what we want to do actually is always pull into a unification of containers-storage and composefs, and then (reflink) copy from one/both of those into ostree.

That would mean we wouldn't need to make any up-front decision about storage based on the input container.

In the very short term, probably the simplest thing here is to always default to ostree if we're being run from outside a container.

[KKoukiou]

Could you try specifying --bootloader grub in the bootc install invocation here? https://github.com/rhinstaller/anaconda/blob/0fa1c7a2f271ba1ed5dd1456def57a7295efb5cc/pyanaconda/modules/payloads/payload/rpm_ostree/installation.py#L833

Yes it looks like it resolved the issue: rhinstaller/anaconda#6765
@cgwalters @ckyrouac so it's ok to hardcode? Can you provide with a short hint why this is needed to comment on the anaconda code?

[KKoukiou]

@cgwalters @ckyrouac how would that behave on s390 installations if we hardcode grub for bootloader? Will this be ignored if not available or it would now fail?

[cgwalters]

I'm working on fixing this in bootc.

Could probably work around in Anaconda for now by only passing --bootloader if the architecture is not s390x.