I have asked the beaker(using pxeboot) infra synced IoT compose to beaker repo, the installation failed[1],so I try to check whether pxeboot works well locally,turns out it doesn't,failed with: Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried FYI:I'm able to perform an pxeboot installation with 38 repo Reproducible: Always
Created attachment 1960717 [details] anaconda.log
Created attachment 1960718 [details] syslog
Created attachment 1960719 [details] packaging.log
Please provide details of what you're trying to do, IoT doesn't use dnf and the standard rpm repo data so I suspect it's a configuration issue on your side. Also for IoT/Edge we don't typically support PXE as a whole as it's an insecure mechanism and hard to support in Edge use cases so our officially supported network deployment model is UEFI HTTP boot which has been part of the UEFI spec for well over a decade.
I was trying to use beaker bare metal servers to run some IoT testcases automatically. I was not sure whether IoT supports pxeboot,so before I asked the beaker infra to sync IoT repo, I do checked with Fedora-IoT-ostree-38.20230419.2-20230419.2.x86_64.iso locally using virt-manager, by following this page[1],and the pxeboot installation works well. [1]https://fedoraproject.org/wiki/QA:Testcase_Boot_Methods_Pxeboot > Also for IoT/Edge we don't typically support PXE as a whole as it's an insecure mechanism and hard to support in Edge use cases so our officially supported network deployment model is UEFI HTTP boot which has been part of the UEFI spec for well over a decade. So,it doesn't make much sense to test IoT on beaker servers?Please feel free to close this bug then.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.