Issue #1687
closed
Document that RHEL6 and lower cannot kickstart from lazy repositories
Description
The version of Anaconda that ships with EL6 does not follow HTTP 302 redirects. For this reason, it is not possible to kickstart EL6 or less from an `on_demand` or `background` repository that doesn't already have all the necessary files downloaded.
This should be noted in the alternate download policy documentation prior to the release of 2.8.
Updated by mhrivnak over 7 years ago
Before proceeding, we'll need PM feedback on whether this is acceptable, or whether we need to get creative and find a way. There are at least a couple of options we could pursue if necessary to make anaconda work in this case.
Updated by jcline@redhat.com over 7 years ago
- Status changed from NEW to CLOSED - NOTABUG
It turns out I made the same configuration error the original reporter made. The VM hostname resolves on the host machine, but not on other guest machines. The default value for the `redirect_host` is the FQDN of the host. Therefore it was possible to start the kickstart process, but once the guest booted and started requesting addition content, it failed to resolve the hostname of the repository. The result was the initial request would arrive, get a HTTP 302 with an unresolvable host and no second request would appear on the server side.
.