View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0017961||CentOS-8||anaconda||public||2020-12-18 16:27||2020-12-30 08:20|
|Target Version||Fixed in Version|
|Summary||0017961: 8.3.2011 install ISOs can't use network repos with kickstart files|
|Description||Based on my testing the CentOS-8.3.2011-x86_64-dvd1.iso and CentOS-8.3.2011-x86_64-boot.iso don't appear to work using a kickstart file, if you specify a network repo. I tried a variety of repo urls including BaseOS/x86_64/os/ (which should work), along with BaseOS/x86_64/os/media.repo and BaseOS/x86_64/kickstart/. I tried pointing the kickstart file at the 8.2.2004 repos on the vault server. I tried HTTP and HTTPS. Nothing seemed to work. Note, I asked for the text installer in my kickstart file. I also tried changing the name of the repo, in case that was the issue.|
If I boot from the 8.2.2004 install ISOs, everything works just fine, whether it's pointed at the 8.2.2004 repo, or the 8.3.2011.
I have previously installed 8.3.2011 over the network, manually, using the graphical installer, so I know that works just fine. So this might only be an issue with the text installer, and/or if a kickstart file is in use.
I'm a attaching a kickstart file for testing. Note this kickstart file works just fine using the DVD installer, with the network repos disabled.
|Steps To Reproduce||Boot and try installing with the provided kickstart file.|
|Tags||No tags attached.|
centos8.ks (646 bytes)
|I was looking over some of my configs, and realized I've done successful network installs using the 8.3.2011 ISOs and the graphical installer. So this issue is probably specific to the anaconda text installer.|
This URL works for me: url --mirrorlist="http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=BaseOS&infra=$infra"
The whole kickstart file is available here: https://github.com/nmusatti/packer-centos8/blob/master/http/kickstart.cfg
Note that, as I explain in issue #0017940, if I use it in the graphical installer only a few of the usual software options are available.
nmusatti were you able to get it working if you specify the repo URL instead of the mirrorlist? And more importantly, what happens if that repo URL uses HTTPS?
As a rule, I try I avoid using HTTP, and the mirrorlist server doesn't support requests over HTTPS or (last I checked), returning HTTPS URLs.
Also, when i did my testing, I checked the mirrorlist URL and tried providing the URLs directly, so I find it strange that they would work if provided via the mirrorlist, but don't work when dictated directly.
|I never tried anything different from a mirrorlist URL, nor https variations, sorry.|