I am testing a CentOS 7.6 kickstart installation. After kickstart was initiated, the installation stops at some point where a sort of table is printed under "Installation", and the item that fails is 4 - Software selection, Error checking software selection. I have checked /tmp/packaging.log and /tmp/anaconda.log, but cannot find any errors here that would prevent installation. Poor error messages, no usable lead for debug.
On 03/06/2019 07:12 AM, isdtor wrote:> I am testing a CentOS 7.6 kickstart installation. After kickstart was initiated, > the installation stops at some point where a sort of table is printed under > "Installation", and the item that fails is 4 - Software selection, Error > checking software selection. > > I have checked /tmp/packaging.log and /tmp/anaconda.log, but cannot find any > errors here that would prevent installation. > > Poor error messages, no usable lead for debug. > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >Hi, I have run into this - in my experience it means there is some dependency missing. And you are correct trying to find the error is a PITA. Steve
At least for debugging, try adding "inst.graphical" to the "append initrd=" line in your isolinux.cfg on the .iso image (grub.cfg and the "linuxefi" line if you are booting UEFI). Remove "inst.cmdline" and "inst.text", as well as any entries of " inst.noninteractive", " inst.noshell" and " inst.headless" from the same "append" line, as they will make troubleshooting more difficult/impossible. Once you are in the graphical Anaconda, it will take a few seconds to check the settings from the kickstart file (you will see "warning" bars on various config sections while it verifies the settings). When only the Packages section still has a warning bar, click on it and see if that helps identify the missing dependencies. I could be wrong, but you might also find a yum.log in the /tmp/ folder of the LiveOS image while Anaconda is still running (I think it's <ALT-2> to switch to the second console in Anaconda, but I could have the wrong key-combo). Gregory -----Original Message----- From: CentOS <centos-bounces at centos.org> On Behalf Of Steve Clark Sent: March 6, 2019 7:48 AM To: centos at centos.org Subject: Re: [CentOS] CentOS 7.6 kickstart error On 03/06/2019 07:12 AM, isdtor wrote:> I am testing a CentOS 7.6 kickstart installation. After kickstart was > initiated, the installation stops at some point where a sort of table > is printed under "Installation", and the item that fails is 4 - > Software selection, Error checking software selection. > > I have checked /tmp/packaging.log and /tmp/anaconda.log, but cannot > find any errors here that would prevent installation. > > Poor error messages, no usable lead for debug. > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >Hi, I have run into this - in my experience it means there is some dependency missing. And you are correct trying to find the error is a PITA. Steve _______________________________________________ CentOS mailing list CentOS at centos.org https://lists.centos.org/mailman/listinfo/centos
Steve Clark writes:> On 03/06/2019 07:12 AM, isdtor wrote: > > I am testing a CentOS 7.6 kickstart installation. After kickstart was initiated, > > the installation stops at some point where a sort of table is printed under > > "Installation", and the item that fails is 4 - Software selection, Error > > checking software selection. > > > > I have checked /tmp/packaging.log and /tmp/anaconda.log, but cannot find any > > errors here that would prevent installation. > > > > Poor error messages, no usable lead for debug. > > > Hi, > > I have run into this - in my experience it means there is some dependency missing. > And you are correct trying to find the error is a PITA.I figured out a different way, less involved than the one proposed by Gregory. The package selection in the kickstart file essentially consists of a custom group to keep it short. So I took a 7.5 machine and then ran a group update off the 7.6 custom repo. The packages that make the update fail are new in 7.6, and the 7.6 kickstart started working once I removed them from the repo. They were the grub2-ppc* packages.