Description of problem: 1. Use a UEFI-based system. 2. create a kickstart file containing `bootc` and `autopart` or `reqpart`, e.g. ``` zerombr clearpart --all --initlabel autopart bootc --source-imgref=registry:quay.io/fedora/fedora-bootc:rawhide ``` 3. use ` mkksiso --ks ./test.ks ./Fedora-Server-dvd-x86_64-Rawhide-20260106.n.0.iso ./test.iso` to embed the kickstart file into the latest rawhide server ISO file to automate installation. 4. Use said test.iso file to provision a machine. Version-Release number of selected component: anaconda-44.11 The following was filed automatically by anaconda: anaconda 44.11 exception report Traceback (most recent call first): File "/usr/lib/python3.14/site-packages/dasbus/client/handler.py", line 509, in _handle_method_error raise exception from None File "/usr/lib/python3.14/site-packages/dasbus/client/handler.py", line 483, in _get_method_reply return self._handle_method_error(error) File "/usr/lib/python3.14/site-packages/dasbus/client/handler.py", line 450, in _call_method return self._get_method_reply( File "/usr/lib64/python3.14/site-packages/pyanaconda/ui/gui/spokes/installation_progress.py", line 78, in _on_installation_done self._task_proxy.Finish() File "/usr/lib/python3.14/site-packages/dasbus/signal.py", line 53, in emit callback(*args, **kwargs) File "/usr/lib/python3.14/site-packages/dasbus/client/handler.py", line 365, in _signal_callback callback(*unwrap_variant(parameters)) File "/usr/lib/python3.14/site-packages/dasbus/client/handler.py", line 133, in _signal_callback callback(parameters, *callback_args) pyanaconda.modules.common.errors.installation.PayloadInstallationError: Bootc installation does not yet support user-specified mount points. Unsupported mount points: /boot/efi Additional info: cmdline: /usr/bin/python3 /usr/bin/anaconda executable: /usr/bin/anaconda hashmarkername: anaconda product: Fedora reason: pyanaconda.modules.common.errors.installation.PayloadInstallationError: Bootc installation does not yet support user-specified mount points. Unsupported mount points: /boot/efi package: anaconda-44.11 release_type: pre-release type: anaconda release: Fedora release 44 (Rawhide) cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-rawh rd.live.check quiet inst.ks=hd:LABEL=Fedora-S-dvd-x86_64-rawh:/test.ks addons: com_redhat_kdump kernel: 6.18.0-65.fc44.x86_64 version: rawhide
Created attachment 2121340 [details] File: anaconda-tb
Created attachment 2121341 [details] File: ks.cfg
Created attachment 2121342 [details] File: backtrace
Created attachment 2121343 [details] File: os_info
Created attachment 2121344 [details] File: environ
Created attachment 2121345 [details] File: syslog
Created attachment 2121346 [details] File: description
Created attachment 2121347 [details] File: storage.log
Created attachment 2121348 [details] File: packaging.log
Created attachment 2121349 [details] File: program.log
Created attachment 2121350 [details] File: nmcli_dev_list
Created attachment 2121351 [details] File: lvm.log
Created attachment 2121352 [details] File: anaconda.log
Created attachment 2121353 [details] File: lorax-packages.log
Created attachment 2121354 [details] File: lsblk_output
Created attachment 2121355 [details] File: dbus.log
Created attachment 2121356 [details] File: packaging.log
It seems like /boot/efi (which gets automatically created by `autopart`) is not in the list of accepted partitions: https://github.com/rhinstaller/anaconda/blob/7fd0cfb4853f51aa3c2f3296dee7844f73529795/pyanaconda/modules/payloads/payload/rpm_ostree/installation.py#L766. Whether this omission was intentional I cannot say.
FEDORA-2026-6d27d369dc (anaconda-44.14-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-6d27d369dc
FEDORA-2026-f6e496720b (anaconda-44.14-2.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-f6e496720b
FEDORA-2026-f6e496720b (anaconda-44.14-2.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.