similar to: CentOS 7.6 kickstart error

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

Hi All, I'm trying to figure out where the inittab is for a pxeboot/kickstart installation so that I can disable virtual terminals that allow for interactive input such as CTRL+ALT+F2. I've looked in the /etc directories for the pxeboot initrd as well as the stage2 and minstg2 files. Am I missing something grossly obvious here? -- James A. Peltier Systems Analyst (FASNet),

Gordon Messmer writes: > On 10/21/19 6:38 AM, isdtor wrote: > > Booting with CentOS6 /boot/efi/EFI/redhat/grub.efi, and the older style pxe config file as per ... results in a grub (legacy) prompt on the target machine. > > > Have you tried using the file from the installation tree? > > http://centos.s.uw.edu/centos/6/os/x86_64/EFI/BOOT/ > > or with files

Pete Biggs writes: > On Tue, 2019-07-30 at 13:24 -0400, John Chludzinski wrote: > > I've been doing a CentOS 7.6.1810 net-install since last night. The machine > > seems ok but has been stuck with "performing post-installation setup tasks" > > for hours. This is an old Dell T5400 box, so it isn't blazing fast but ... > > > > Is there a way to

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

Is it not possible to use an nfs based repo for kickstart under CentOS 7.5? E.g. repo --name=epel --baseurl=file://server/path/to/local/copy/of/epel With trial and error I figured out that this is the correct syntax to use for an nfs-based repo. But packages from this repo in the %packages section are not found. You have specificed that the package 'bla' should be installed. This

On Fri, Dec 14, 2018 at 10:04 AM isdtor <isdtor at gmail.com> wrote: > > > > So the syntax looks to be > > > > > > repo --name=epel --baseurl=nfs://server:/path > > > > > > that colon after server is not a spelling error. > > > https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#id48 > > > > That seems to work

I'm trying to autoinstall a DELL 9030 desktop with CentOS7 using PXE and Kikstart. I fall in a strange problem (I have several other laptop or desktop using this install process without any problem, kernel and initrd are from a Centos 7.4 iso) - PXE boot start and the desktop load the kernel and the inirtd file - the kernel is booted and at this time the led of the network switch goes down

Stephen John Smoogen writes: > On Fri, 14 Dec 2018 at 05:02, isdtor <isdtor at gmail.com> wrote: > > > > Is it not possible to use an nfs based repo for kickstart under CentOS 7.5? > > > > E.g. > > > > repo --name=epel --baseurl=file://server/path/to/local/copy/of/epel > > > > So the syntax looks to be > > repo --name=epel

Hi, Is is possible to use kickstart file to install rhel from dvd drive? Mainly idea is to clone one anaconda.ks file to about twenty machines.? examples? ftp/http/dhcp is not possible due to network limitations. -- Eero

Am 08.05.20 um 13:53 schrieb isdtor: > Here's another interesting observation. > > For previous versions, I was able to reduce the size of the updates mirror significantly by running repomange -o and deleting the resulting files on next sync. With the AppStream repo, this no longer works, the anaconda installer will complain that at least one package has an incorrect checksum, and

Hi all, This the latest output from anaconda.log:- 06:08:54,828 DEBUG anaconda: new disk order: [] 06:08:54,832 DEBUG anaconda: new disk order: [] 06:08:54,851 DEBUG anaconda: stage1 device cannot be of type disk 06:08:54,865 DEBUG anaconda: _is_valid_disklabel(sda1) returning True 06:08:54,867 DEBUG anaconda: _is_valid_size(sda1) returning True 06:08:54,867 DEBUG anaconda:

I have a kickstart file that I am using to install multiple machines. If I install with no %post script, everything runs great. When I add the following %post section, if fails. I have been working on this for a few days now without luck, Any help would be appreciated. Here is the error, the script follows. Traceback (most recent call first): File

Are there still a lot of rough edges in this area? There are some things I simply can't get to work. This is about kickstart installations. Finding the right stuff for the %packages sections is lucky dip at best. The RHEL manual points to the comps file, really? This file isn't meant to be parsed by humans. Specifying an environment - the example "Infrastructure Server"

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 - I've been throwing the question around on the kickstart-list for the last few days here, and can't quite get ahold of things. Please, allow me to explain. I am in the process of making a custom CentOS/RHEL kickstart install. It works well right now; however, it's a hackjob, and I am not comfortable with it as of yet. For the past few days, I've even gone as far as

Hi, I'm working on automating virtual machine installs using kickstart files and virt-install. The problem I have is that these kickstart installations install different packages than a minimal manual install. While I got rid of some of them I can't seem to prevent ConsoleKit from getting installed. I put "-ConsoleKit" in the packages section and later also added packages that

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

I've searched around but haven't found a definitive answer yet, is it possible to kickstart from a tagged VLAN? I found this bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=431915 But I can't find out how far the vlan support goes. I haven't found anything about it in any kickstart docs. I have two tagged vlans: Vlan 100 - server subnet Vlan 101 - backup subnet From

Does anyone know how anaconda partitioning enumerates disk partitions when specified in kickstart? I quickly browsed through the anaconda installer source on github but didn't see the relevant bits. I'm using the centOS 6.10 anaconda installer. Somehow I am ending up with my swap partition on sda1, /boot on sda2, and root on sda3. for $REASONS I want /boot to be the partition #1 (sda1)