Hide Forgot
Description of problem: In kickstart I'm missing in keyword repo (for adding extra repository) parameter for setup gpgcheck. I'm installing from added repo for RHEL5 xfsprogs and without setting parm gpgcheck to 0 it would not I have workaround to do it in %post block but I think this parameter should be useful for many users. Version-Release number of selected component (if applicable): RHEL5.8 Expected results: added parameter to repo keyword for setup gpgcheck.
What problem are you seeing? anaconda does not do GPG checking by default, and there's not even any code to do so.
Hi Chris, If anaconda doesn't do this what is a reason that xfsprogs wasn't installed. Please try run in beaker xml I attached. Anaconda installation will stop at phase when is installing xfsprogs. And when I will have in kickstart this %post echo "[xfs-repo]" >> /etc/yum.repos.d/xfs.repo echo "name=xfs-repo" >> /etc/yum.repos.d/xfs.repo echo "baseurl=http://download.lab.bos.redhat.com/rel-eng/repos/dist-5E-xfs-qu-candidate/x86_64" >> /etc/yum.repos.d/xfs.repo echo "enabled=1" >> /etc/yum.repos.d/xfs.repo echo "gpgcheck=0" >> /etc/yum.repos.d/xfs.repo yum -y install xfsprogs it works for me without problems. This repo --name=xfsprogs --baseurl=http://download.lab.bos.redhat.com/rel-eng/repos/dist-5E-xfs-qu-candidate/x86_64 doesn't work for me. Thanks Kamil
Created attachment 557685 [details] xml with kickstart and added repo
I can't speculate on why an install failed without seeing the log files from the installation. Please attach them as individual attachments.
I got this message in console during installation. The file xfsprogs-2.10.2-7.el5.x86_64.rpm cannot be opened. This is due to a missing file, a corrupt package or corrupt media. Please verify your installation source. If you exit, your system will be left in an inconsistent state that will likely require reinstallation. Reboot Retry That is failed job https://beaker.engineering.redhat.com/jobs/185031 I will attached logs as you requested.
Created attachment 557693 [details] Anaconda.log
Created attachment 557695 [details] ks.cfg
The file referenced at the end of the anaconda.log does not exist. This appears to be some sort of repo problem.