Description of problem:
Network (NFS) install fails when ISOs not belonging to RHEL are in
same directory as RHEL ISOs.
I have a centralized file server, isis. It is exporting "/netinstall"
via NFS, for network installs of various software -- FreeBSD, Fedora
Core 2, RHEL, etc. Both FreeBSD and Fedora install just fine from this
shared repository, whereas RHEL seems to be getting jealous and
refuses to install. When I use a tried-and-true kickstart file for
RHEL, it complains about missing files and corrupt CDs right as it
would start to snag files. However, if I remove the other OS
distribution ISOs from that directory, leaving just RHEL ISOs and the
kickstart config, it works flawlessly.
I have attached my kickstart configuration file for reference.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up an NFS server as you normally would for a kickstart/NFS install.
2. Populate the exported filesystem with RHEL ISOs and kickstart
3. Add other ISO files to same exported filesystem that do not belong
to the RHEL distribution.
4. Attempt kickstart installation using NFS (linux ks=nfs:server:/export)
Actual Results: After kickstart begins, Anaconda spews thousands of
lines of warnings about files missing from the distribution.
Expected Results: The install should have succeeded, as the files are
in the right place, accessable, and have been verified good.
Created attachment 102573 [details]
This is as it should be, there's no way to really match up between the
boot image and the ISOs.
One set of install ISOs per directory is the rule.
Hopefully the correct functionality as it works in Fedora will be
backported, since it is functional and acceptable behavior. Clearly
Fedora's version of anaconda is more intelligent. Thanks.