Description of problem: Attempting to pxe boot the latest Fedora 33 nightly (Fedora-33-20200816.n.0) fails to read the initrd.img error: ../../grub-core/net/net.c:1795:timeout reading `/fedora/Fedora-33-20200816.n.0/Everything/initrd.img'. Version-Release number of selected component (if applicable): grub2-2.04-28.fc33 Additional info: Replacing grubaa64.efi from an earlier compose (Fedora-Rawhide-20200811.n.0) worked as expected.
Proposing as a blocker for F33 beta, criteria "It must be possible to install by booting the installation kernel directly (including via PXE) and correctly specifying a remote source for the installer itself."
Discussed during the 2020-08-17 blocker review meeting: [0] The decision to classify this bug as an "AcceptedBlocker" was made as it violates the following criterion: "It must be possible to install by booting the installation kernel directly (including via PXE)...", specifically concerning aarch64. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-08-17/f33-blocker-review.2020-08-17-16.11.txt
Same error with grub2-2.04-27.fc33
I was also able to reproduce this issue. With grub2-2.04-27.fc33: grub> linux /images/pxeboot/vmlinuz grub> initrd /images/pxeboot/initrd.img error: ../../grub-core/net/net.c:1795:timeout reading `/images/pxeboot/initrd.img'. grub> echo $? 28 With grub2-2.04-25.fc33: grub> linux /images/pxeboot/vmlinuz grub> initrd /images/pxeboot/initrd.img grub> echo $? 0
Created attachment 1711746 [details] grubaa64.efi Could you please test using the attached grubaa64.efi binary?
(In reply to Javier Martinez Canillas from comment #5) > Created attachment 1711746 [details] > grubaa64.efi > > Could you please test using the attached grubaa64.efi binary? That works.
(In reply to Paul Whalen from comment #6) > (In reply to Javier Martinez Canillas from comment #5) > > Created attachment 1711746 [details] > > grubaa64.efi > > > > Could you please test using the attached grubaa64.efi binary? > > That works. Thanks for testing. It's a build that drops the following patch: https://src.fedoraproject.org/rpms/grub2/blob/f33/f/0238-tftp-Do-not-use-priority-queue.patch I will dig deeper why that patch is leading to the TFTP regression.
FEDORA-2020-6888b64b0d has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-a75d237bd0 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-9d7c0d5262 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-959fec6242 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-959fec6242
FEDORA-2020-959fec6242 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-959fec6242` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-959fec6242 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Is it possible to backport the fix to Fedora 32? I am seeing this problem with Fedora 32 on aarch64.
FEDORA-2020-a15f088661 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-a15f088661
(In reply to Prashanth Sundararaman from comment #13) > Is it possible to backport the fix to Fedora 32? I am seeing this problem > with Fedora 32 on aarch64. Backported this to F32 and pushed an update.
FEDORA-2020-a15f088661 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-a15f088661` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-a15f088661 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-a15f088661 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-959fec6242 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-976bd8ab94 has been pushed to the Fedora ELN stable repository. If problem still persists, please make note of it in this bug report.