Hello everyone,
I want to start using cobbler for my installations. So, I have setup cobbler packages in my home server.
When I go to the “cobbler check”, I see the following issues:
cobbler check
The following are potential configuration items that you may want to fix:
2 : Apache (httpd) is not installed and/or in path
4 : ksvalidator was not found, install pykickstart
Besides 4, which I suppose that I cannot find it in any openSUSE repository, my question is about 2. My home server has apache configured and that apache servers over 12 internal web sites. Does anybody knows what to do about it?
I will test the src.rpm of ksvalidator.
AS for the prerequisites, yes. I used zypper, so no dependencies issue. As I said, it’s just a warning that it should not appear (apache is installed).
Well, it seems that installation was completed. But not in the way that I had requested to! Look at the configuration of my test system.
The system is configured as:
cobbler system report
Name : test
TFTP Boot Files : {}
Comment :
Fetchable Files : {}
Gateway : 192.168.0.1
Hostname : testcob1.home
Image :
IPv6 Autoconfiguration : False
IPv6 Default Device :
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart : <<inherit>>
Kickstart Metadata : {}
LDAP Enabled : False
LDAP Management Type : authconfig
Management Classes : ]
Management Parameters : <<inherit>>
Monit Enabled : False
Name Servers : '192.168.0.1', '192.168.0.2']
Name Servers Search Path : ]
Netboot Enabled : False
Owners : 'admin']
Power Management Address :
Power ID :
Power Password :
Power Management Type : ipmitool
Power Username :
Profile : RHEL-6.5-x86_64
Proxy : <<inherit>>
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Repos Enabled : False
Server Override : <<inherit>>
Status : testing
Template Files : {}
Virt Auto Boot : <<inherit>>
Virt CPUs : <<inherit>>
Virt Disk Driver Type : <<inherit>>
Virt File Size(GB) : <<inherit>>
Virt Path : <<inherit>>
Virt RAM (MB) : <<inherit>>
Virt Type : <<inherit>>
Interface ===== : eth0
Bonding Opts :
Bridge Opts :
DHCP Tag :
DNS Name :
Master Interface :
Interface Type :
IP Address : 192.168.0.200
IPv6 Address :
IPv6 Default Gateway :
IPv6 MTU :
IPv6 Secondaries : ]
IPv6 Static Routes : ]
MAC Address :
Management Interface : True
MTU :
Subnet Mask : 255.255.255.0
Static : True
Static Routes : ]
Virt Bridge :
However, the installed system has not set the hostname correctly (it is localhost.localdomain), the networking is set to DHCP instead of static/192.168.0.200 and of course no DNS are set! Yes, I did kickstarted the target system more than once, after cobbler sync and cobbler restart etc. It is always the same system. Is seems like the kickstart is not updated!
The kickstart used in the installation is:
#platform=x86, AMD64, or Intel EM64T
# System authorization information
auth --useshadow --enablemd5
# System bootloader configuration
bootloader --location=mbr
# Partition clearing information
clearpart --all --initlabel
# Use text mode install
text
# Firewall configuration
firewall --enabled
# Run the Setup Agent on first boot
firstboot --disable
# System keyboard
keyboard us
# System language
lang en_US
# Use network installation
url --url=http://192.168.0.1/cblr/links/RHEL-6.5-x86_64
# If any cobbler repo definitions were referenced in the kickstart profile, include them here.
repo --name=source-1 --baseurl=http://192.168.0.1/cobbler/ks_mirror/RHEL-6.5-x86_64
repo --name=source-2 --baseurl=http://192.168.0.1/cobbler/ks_mirror/RHEL-6.5-x86_64/ScalableFileSystem
repo --name=source-3 --baseurl=http://192.168.0.1/cobbler/ks_mirror/RHEL-6.5-x86_64/HighAvailability
repo --name=source-4 --baseurl=http://192.168.0.1/cobbler/ks_mirror/RHEL-6.5-x86_64/ResilientStorage
repo --name=source-5 --baseurl=http://192.168.0.1/cobbler/ks_mirror/RHEL-6.5-x86_64/Server
repo --name=source-6 --baseurl=http://192.168.0.1/cobbler/ks_mirror/RHEL-6.5-x86_64/LoadBalancer
# Network information
network --bootproto=dhcp --device=eth0 --onboot=on
# Reboot after installation
reboot
#Root password
rootpw --iscrypted $1$co.TJRhD$cVrSY0pGDmpROtk1ToLYO1
# SELinux configuration
selinux --disabled
# Do not configure the X Window System
skipx
# System timezone
timezone America/New_York
# Install OS instead of upgrade
install
# Clear the Master Boot Record
zerombr
# Allow anaconda to partition the system as needed
autopart
%pre
set -x -v
exec 1>/tmp/ks-pre.log 2>&1
# Once root's homedir is there, copy over the log.
while : ; do
sleep 10
if -d /mnt/sysimage/root ]; then
cp /tmp/ks-pre.log /mnt/sysimage/root/
logger "Copied %pre section log to system"
break
fi
done &
wget "http://192.168.0.1/cblr/svc/op/trig/mode/pre/profile/RHEL-6.5-x86_64" -O /dev/null
# Enable installation monitoring
%packages
%post
set -x -v
exec 1>/root/ks-post.log 2>&1
# Start yum configuration
wget "http://192.168.0.1/cblr/svc/op/yum/profile/RHEL-6.5-x86_64" --output-document=/etc/yum.repos.d/cobbler-config.repo
# End yum configuration
# Start post_install_network_config generated code
# End post_install_network_config generated code
# Start download cobbler managed config files (if applicable)
# End download cobbler managed config files (if applicable)
# Start koan environment setup
echo "export COBBLER_SERVER=192.168.0.1" > /etc/profile.d/cobbler.sh
echo "setenv COBBLER_SERVER 192.168.0.1" > /etc/profile.d/cobbler.csh
# End koan environment setup
# begin Red Hat management server registration
# not configured to register to any Red Hat management server (ok)
# end Red Hat management server registration
# Begin cobbler registration
# cobbler registration is disabled in /etc/cobbler/settings
# End cobbler registration
# Enable post-install boot notification
# Start final steps
wget "http://192.168.0.1/cblr/svc/op/ks/profile/RHEL-6.5-x86_64" -O /root/cobbler.ks
wget "http://192.168.0.1/cblr/svc/op/trig/mode/post/profile/RHEL-6.5-x86_64" -O /dev/null
# End final steps
OK, the openSUSE documentation saved the day and I managed to find out what was wrong in the first part of it. It seems that the only way to distinguish a system is via a MAC address. So, when you configure a system, in reality you configure a very specific hardware/vm, not a class.