Kickstart Generator

how to get access to this lab ?

the web page in email information about the availability of tool says "not found" : https://access.redhat.com/labs/kickstartconfig/

I'm seeing page not found:

Not Found

The page you are looking for is not here. It might have been moved, removed, or had its name and address changed. It might otherwise be temporarily unavailable for technical reasons.

The good news is that you can probably find what you are looking for by searching the site.

Works for me!

yep, works now from firefox.

Under RHEL 6, the manual partitioning doesn't work correctly. Multiple problems to include, can't specify a mount point other than what is on the list, no option to create a LVM partition, selecting file system type of swap and then realizing you made a mistake, you change it to ext4, but can't do anything else. Click OK and it shows swap and not ext4. So, still some work to do.

RHEL7 should have option for LVM and additional single packages to be installed. As well as maybe a hostname.

Nice clean app for a 'starting' kickstart though.

Dear Red Hat folks, thank you much for making this Kickstart configuration tool in the access labs of access.redhat.com. It would be great if while using this, one could enter the size of the drive they're using, and then also configure LVM systems instead of simple non-lvm partitions. Additionally, if one could at least assign labels if no LVM was available in this - it would be nice.

When I posted this, it didn't allow me to see the context of the other messages preceding. I now see that LVM for this access lab will be considered for a future edition.

Thanks much

ADDED
I put in a basic set of kickstart directives and ended up with this:
(However, I added the note in the block below with the Red Hat solution on partitioning)

lang en_US
keyboard us
timezone America/New_York --isUtc
rootpw $1$WCQgf2dQ$n3GrnPUheO52h1QxVSuRy0 --iscrypted
#platform x86, AMD64, or Intel EM64T
text
cdrom
###
#### NOTE: SEE THIS ARTICLE REGARDING IMPORTANT PARTITIONING INFO IN THE NEXT LINE
#### https://access.redhat.com/solutions/19584
###  Using bare device names without labels or LVM is usually a bad idea, see above article
##
bootloader --md5pass=$1$MBfLKouI$AJqqq.CCI3oz7zmFBvKzG. --location=mbr --append=rhgb,quiet,crashkernel=auto
zerombr
clearpart --all --initlabel
part --fstype=xfs /boot --size=500 --asprimary
part --fstype=swap --size
part --fstype=xfs /tmp --size=4096 
part --fstype=xfs / --size=25000
part --fstype=xfs /var --size=8192
part --fstype=xfs /usr --size=12388
auth --passalgo=sha512 --useshadow
selinux --enforcing
firewall --enabled --ssh
firstboot --disable
%post --interpreter=/bin/bash
echo "your post script goes after this line"
%end

My sample today with lvm added:

lang en_US
keyboard us
timezone America/New_York --isUtc
rootpw $1$4Id71t44$NcJMzq4kFN8Fx4yG.RmUr/ --iscrypted
#platform x86, AMD64, or Intel EM64T
text
cdrom
bootloader --md5pass=$1$4Zwyncv3$9Drh8KBuaUySCKBRNUC2o0 --location=mbr --append=rhgb,quiet,crashkernel=auto
zerombr
clearpart --all --initlabel
volgroup disk0 --pesize=4096 pv.0 
part pv.0 --fstype=lvmpv --ondisk=sda --size=204800
logvol /boot --vgname=disk0 --name=boot --fstype=xfs --size=500
logvol / --vgname=disk0 --name=slash --fstype=xfs --size=32000
logvol /var/log/audit --vgname=disk0 --name=varlogaudit --fstype=xfs --size=4096
logvol /tmp --vgname=disk0 --name=tmp --fstype=xfs --size=1
logvol /var --vgname=disk0 --name=var --fstype=xfs --size=16384
logvol /var/log --vgname=disk0 --name=varlog --fstype=xfs --size=1
auth --passalgo=sha512 --useshadow
selinux --enforcing
firewall --enabled --ssh
firstboot --disable
%pre --interpreter=/bin/bash
echo "this is a pre script, enter your directives in this location"
%end
%post --interpreter=/bin/bash
echo "this is a post script, enter your post directives here."
%end

even tho passwords are the same, it still complains it not.

The kickstart configuration tool would be much more useful if you could read in an existing kickstart script and use the configurator to modify it.

there's one more small bug in the kickstart tool that I've found. If you customize the kernel options for the bootloader command, the tool creates the bootloader directive with commas between the options rather than spaces. The kernel seems to ignore the options in this case. (i'd show an example, but this submit box is tiny)

EDIT: If I change the kernel options to remove the crashkernel=auto option, the bootloader directive is generated as
bootloader --location=mbr --boot-drive=sda --append=rhgb,quiet
when it should be
bootloader --location=mbr --boot-drive=sda --append="rhgb quiet"

This may just be because the kernel option line in the tool mistakenly puts commas between the options and the user simply follows the same format.

As soon as I enter a character in "Root Password:" box a heading comes up that states, "Root Password doesn't match". This never goes away so I cannot download the kickstart!

Hi team,

I'm planning to create USB Boot drive via image RHEL 6.7 , how can I use the generated file from Kick Start from this tool to automate the installation?

-Ashraf EMAM,

Error creating kickstart config file... [object Object]

EdSearch01Q

scr

[hello|javascript:alert(1)]

https://access.redhat.com/labs/kickstartconfig/ gives 404...

It would nice if you had link on this page to the kickstart options documentation.

Is there any way to tell kickstart to use and configure the active NIC interface (since eth0 does not work in 7.2 anymore):

From my kickstart.cfg: " network --device=eth0 --bootproto=static --ip=x.y.145.36 --netmask=255.255.255.0 --gateway=x.y.145.254 --nameserver=x.y.30.91 " With this new naming convention every machine will likely have a different name for the active NIC. I have already seen "enp5s0" and "ens32"... Need some predictability and uniformity... Please help if you have any leads.