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.
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '39'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 39 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26. Fedora Linux 39 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.