I am trying to install AlmaLinux 8.4 from a local PXE server, but I am running into “Error setting up software source” right at the start of the installation every single time. There’s no other apparent issues.
The installation files were originally extracted from an AlmaLinux-8.4-x86_64-dvd.iso, but I’ve also tried installing with a copy of everything downloaded from Index of /almalinux/8.4/. The setup files are located on the local server at http://10.0.0.1/almalinux/8.4/* (tried configuring both from within a kickstart and directly on the setup screen). The files are being served over nginx; after Anaconda pauses on the error and I switch to a virtual terminal, I can verify the required files can be curled and pulled with wget from the system that I am trying to kick. Same thing happens trying to go through text-only setup, but not sure if that would make a difference anyways.
The odd part is this configuration is mirrored across two separate, but nearly-identical environments. One always succeeds and the other always fails. The failing network is more isolated from the outside world than the first, but all required files are hosted within their respective networks. I’ve verified most of the easy stuff like typing in the proper network locations, by comparing systems side by side as they are being kicked on these separate networks. This seems to me to point to either a mismatch of installation files or some configuration on the failing network that is preventing Anaconda from properly recognizing or pulling information from the software source. I’ve verified all of the installation files are identical. I am still working on verifying the vmlinuz and initrd.img files are the same, and I am digging through the Anaconda github (GitHub - rhinstaller/anaconda: System installer for Fedora, RHEL and other distributions) to try and track down what process it uses to verify an installation repo.
Any suggestions? Or has anyone run into similar situations before?