similar to: CentOS 7 KickStart Configurator Issue

On 2019-10-03, isdtor writes: > Is the kickstart repo directive broken under CentOS 7? Every attempt with a repo directive in the kickstart file fails during the software selection step. Removing the repo directives and the packages from those repos under %packages makes it work. > > On console 2, I have verified that the (NFS) repos specified in the kickstart file are mounted and that

Is the kickstart repo directive broken under CentOS 7? Every attempt with a repo directive in the kickstart file fails during the software selection step. Removing the repo directives and the packages from those repos under %packages makes it work. On console 2, I have verified that the (NFS) repos specified in the kickstart file are mounted and that the repo metadata has been copied over to

Over the last couple of weeks, additional software was installed using the package manager. I would like to get a custom kickstart file created for our system. For this, I would like to get complete list of software installed so they may be add to the kickstart file package selection. Can anyone tell me if this can be done? If it can, please give me instructions? Finally, where on

This problem still bites us. I've tried to play around with DHCP settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. I'm happy about /any/ hint. Cheers frank On 04/24/2017 11:57 PM, Frank Thommen wrote: > Hi, > > kickstarting fails due to problems with host resolution, even though the > network seems to be properly configured through DHCP. eno1 and eno2 are

http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/sysadmin-guide/ch-redhat-config-kickstart.html To use Kickstart Configurator, you must be running the X Window System. To start Kickstart Configurator, select Applications (the main menu on the panel) => System Tools => Kickstart, or type the command /usr/sbin/system-config-kickstart. Can't find it. Now my system has:

Hello, I've been trying to kickstart a install centos from a USB memory stick. Everything with that is working fine, but I seem to be having a problem with the ks.cfg file. When I boot the install media from the usb drive, the the boot prompt I type linux ks=hd:/dev/uba1/ks.cfg Then I peek at the logs and it even says * getting kickstart file * getting kickstart file from harddrive *

> On 28 Aug 2016, at 10:04 AM, Chris Murphy <lists at colorremedies.com> wrote: > > On Fri, Aug 26, 2016 at 10:39 AM, Gordon Messmer > <gordon.messmer at gmail.com <mailto:gordon.messmer at gmail.com>> wrote: >> On 08/25/2016 11:35 PM, Phil Manuel wrote: >>> >>> The relevant kickstart section is:- >>> >>> part /boot/efi

On 08/25/2016 11:35 PM, Phil Manuel wrote: > The relevant kickstart section is:- > > part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda > bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1 > autopart --type=lvm A couple of things to consider: * The documentation for "autopart" states that "The autopart command

On Fri, Feb 15, 2019 at 3:01 AM <freebsd at tango.lu> wrote: > I am working on a kickstart automated Centos 7 GUI vm deployment. > > Defining gnome desktop in kickstart works. > @gnome-desktop - A GNOME desktop > > However Centos and anything from the epel-release such as xrdp does not > work. > > I have tried it on different ways. > > > repo

Hello all, I've been struggling with an issue with my kickstart configuration for a while now. My kickstart files are stored within the initrd image. What I would like to do here, is when the kickstart first starts up, I want it to grab a DHCP address (it does at the moment) so it can grab all of the necessary installation data off the net. Then, at some point _IN_ the install process, I'd

Gordon Messmer wrote: > On 08/25/2016 11:35 PM, Phil Manuel wrote: >> The relevant kickstart section is:- >> >> part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda >> bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1 >> autopart --type=lvm > > A couple of things to consider: > * The documentation for

On Fri, Aug 26, 2016 at 10:39 AM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/25/2016 11:35 PM, Phil Manuel wrote: >> >> The relevant kickstart section is:- >> >> part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda >> bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1 >> autopart

I am trying to add an efi partition to my working kickstart file. bootloader --driveorder=sda --append="rhgb quiet biosdevname=0 net.ifnames=0" clearpart --all --initlabel part / --ondisk=sda --fstype xfs --size=20000 --asprimary part swap --ondisk=sda --size=4000 --asprimary part /boot/efi --ondisk=sda --fstype efi --size=1000 --asprimary part /home --ondisk=sda

Hi, all. I'm trying to customize a CentOS installation cd, but got trouble with kickstart. I want to use dialog[1] for command line based user interface, but it can't display correctly in kickstart with CentOS 5.5. Same ks file works with CentOS 5.3 (both i386 and x86_64). What's the different between CentOS 5.3/5.5? I can't find it in release notes. And how can i fix it? Thanks

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

Hi again. I'm pleased to say that my experimentation with ocfs2 has been very successful and I'm considering doing some real work with it. My current question is related to virt-manager and the use of kickstart to install paravirtualised domU's. I'm happily doing fully-virtualised installs with this tool but due to poor network performance I thought it time to do some

Hello, I am working on a kickstart automated Centos 7 GUI vm deployment. Defining gnome desktop in kickstart works. @gnome-desktop - A GNOME desktop However Centos and anything from the epel-release such as xrdp does not work. I have tried it on different ways. repo --name=epel-release %packages #epel-release # DOES NOT WORK @ Core #@core @ Base

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

On Tue, 23 Aug 2016 at 02:18 Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/21/2016 11:56 PM, Phil Manuel wrote: > > part /boot/efi --fstype="efi" --size=200 --ondisk=sda > > And I have tried the latter with location as mbr still fails > > What am I missing ? > > > I very vaguely remember struggling with this as well, but I can't find

Hello all - (Please forgive me if I sent this msg twice, first one didn't seem to go through) I searched through the archives and did not see anything about this (along with google), but if I missed something please don't hesitate to send me some links. Basically I have hit a problem that I cannot figure out at this point and seemed to have ran out of ideas via Google or the