Enable UEFI Red Hat support on Cobbler (2.6.7) - HOW?
by Ž D
Hallo. I was successful in UEFI boot and install, here are details:
1) Cobbler server : 2.6.9
source: ?, ?
build time: Fri Jun 12 07:42:24 2015
Cobbler is installed on Oracle Linux 6.6
2) I am installing Oracle Linux R6-U6-x86_64 on the Oracle Server x3-2
3) DHCP service is provided by another box, the config is:
host my-hostname.domain.com {
hardware ethernet 00:10:e0:aa:aa:aa;
fixed-address 10.xx.xx.xx;
next-server 10.yy.yy.yy; # my cobbler server
filename "/grub/BOOTX64.efi";
}
4) How to find proper BOOTX64.efi file, read the doc:
http://docs.oracle.com/cd/E37670_01/E41137/E41137.pdf
See the paragraph 1.4.7 (starts on page 9), the page 10 talks about
UEFI-based PXE client.
This is the key: UEFI-based PXE clients can use the BOOTX64.efi boot
loader, which is available as EFI/BOOT/BOOTX64.efi from the Oracle Linux
6 Update 6 Media Pack DVD image.
So I placed BOOTX64.efi in <my_cobbler_server>:/var/lib/tftpboot/grub/
5) I also have the file splash.xpm.gz in
<my_cobbler_server>:/var/lib/tftpboot/grub/
6) The file /var/lib/tftpboot/grub/00:10:e0:aa:aa:aa looks like
timeout=10
splashimage=(nd)/splash.xpm.gz
title OL-R6-U6-x86_64-UEFI
root (nd)
kernel /images/OL-R6-U6-x86_64/vmlinuz ksdevice=bootif lang= text
ks=http://my_cobbler_server/cblr/svc/op/ks/system/host_name
initrd /images/OL-R6-U6-x86_64/initrd.img
7) The kickstart file is
# ks for OL 6.6 UEFI
install
text
url --url=http://10.yy.yy.yy/cobbler/links/OL-R6-U6-x86_64
lang en_US.UTF-8
keyboard us
rootpw --iscrypted $1$zw2wh8P1$zZMsVBx4.HbZNxM8p1uPX1
firewall --disabled
authconfig --enableshadow --enablemd5
selinux --disabled
timezone --utc America/Los_Angeles
reboot
bootloader --location=partition
clearpart --all --initlabel
part /boot/efi --fstype=vfat --size=200 --asprimary --ondisk=sda
part /boot --fstype=ext4 --size=500 --label=/boot --asprimary --ondisk=sda
part / --fstype=ext4 --size=8192 --grow --maxsize=51200 --label=/
--ondisk=sda
part /var --fstype=ext4 --size=4096 --label=/var --ondisk=sda
part /u01 --fstype=ext3 --size=4096 --label=/u01 --ondisk=sda
part swap --size=16384 --label=swap --ondisk=sda
%packages
@base
@core
device-mapper-multipath
kexec-tools
net-tools
pciutils
sysfsutils
system-config-kickstart
wget
lsscsi
nfs-utils
8) Works for me. Let me know if you need any other detail?
--
Thanks,
Zarko
7 years, 8 months
Multiple subnets, multiple dhcp --dhcp-tag, profiles, distro
by Tory M Blue
So I'm running into some issues and I'm sure it's a minor brain fart
on my part. But the documentation has not squared me away.
I have a cobbler server running DHCP for 3 networks, my cobbler
server has 3 interfaces and I have 3 dhcp stanzas (whatever).
I can set a different next server, which is the interface IP on that
subnet/vlan. No issue. I can build a system from the 10.13.4 network
just fine. But if I try to build from the 10.13.200 net, I can get a
dhcp address, load the kernel, but the issue is the Distro has the IP
address from the 10.13.4.x network in it so the pxelinux.cfg/default
has the wrong subnet/vlan hardcoded; and thus tries to load the
kickstart
LABEL CentOS7-x86_64_Standard
kernel /images/CentOS7-x86_64/vmlinuz
MENU LABEL CentOS7-x86_64_Standard
append initrd=/images/CentOS7-x86_64/initrd.img ksdevice lang=
kssendmac text
ks=http://10.13.4.101/cblr/svc/op/ks/profile/CentOS7-x86_64_Standard
ipappend 2
So obviously if a host is on the 10.13.200 net, receives a 10.13.200.x
address, and starts booting, cobbler is sending it that kickstart line
and it should not be going to 10.13.4.101 when the local network is
ready to receive at 10.13.200.101.
The metadata tree has the 10.13.4.101 address, and I thought about
setting it to $next_server, but it seems if I do it in the profile via
cobbler_web, it over writes the default file with 10.13.4.101 (the
cobbler host server IP)
I've removed $next-server from the cobbler settings file
#next_server: 10.13.4.101
But server is still configured.
server: 10.13.4.101
So the issue is really the server configuration inside settings. it
mentions --server-override, but I don't want to have a handful of
profiles for the same image.. I would like to just boot up a server
and say use Profile-CentOS-standard and ignore which network it's
coming from., want wildcards or other to figure things out.
Any ideas? really i've been searching and "nothing" I've found has
made me understand where I'm falling short. -dhcp-tags,
--server-override
Thanks
tory
################## DHCP ############
ddns-update-style interim;
allow booting;
allow bootp;
ignore client-updates;
set vendorclass = option vendor-class-identifier;
subnet 10.13.4.0 netmask 255.255.255.0 {
option routers 10.13.4.6;
option domain-name-servers 10.13.4.220, 10.13.7.101, 10.13.7.102;
option domain-name "eng.domain.net";
option subnet-mask 255.255.255.0;
range dynamic-bootp 10.13.4.75 10.13.4.99;
filename "/pxelinux.0";
default-lease-time 21600;
max-lease-time 43200;
next-server 10.13.4.101;
}
subnet 10.13.5.0 netmask 255.255.255.0 {
option routers 10.13.5.6;
option domain-name-servers 10.13.4.220, 10.13.7.101, 10.13.7.102;
option domain-name "eng.domain.net";
option subnet-mask 255.255.255.0;
range dynamic-bootp 10.13.5.220 10.13.5.239;
filename "/pxelinux.0";
default-lease-time 21600;
max-lease-time 43200;
next-server 10.13.5.100;
}
subnet 10.13.200.0 netmask 255.255.255.0 {
option routers 10.13.200.6;
option domain-name-servers 216.249.24.15, 10.13.6.56;
option domain-name "gc.sv.domain.net";
option subnet-mask 255.255.255.0;
range dynamic-bootp 10.13.200.75 10.13.200.85;
filename "/pxelinux.0";
default-lease-time 21600;
max-lease-time 43200;
next-server 10.13.200.101;
}
7 years, 10 months
How Cobbler Triggers Works
by slgray
Hi, I am new to cobbler and I want to use triggers use to do some post
install tasks, suck as create a system profile when the system finish the
first boot from cobbler .
I have read the docs at
http://cobbler.github.io/manuals/2.6.0/4/4/1_-_Triggers.html. But still do
not know how to call the triggers, which url I should send request to.
Hope somebody can provide detail docs for how triggers work, Thanks.
--
*Regards,*
*Slgray*
7 years, 10 months
Re: cobbler managing debian install no CD-ROM detected
by Tony Schreiner
Failed to reply to the list, resend.
On Wed, May 25, 2016 at 4:20 PM, Tony Schreiner <anthony.schreiner(a)bc.edu>
wrote:
> PXE boot with whatever the cobbler profile provides
>
> On Wed, May 25, 2016 at 4:17 PM, <alastair(a)alastair-munro.com> wrote:
>
>> Hi
>>
>> How did u boot? pxe boot or via iso image? if iso image how was this
>> presented? usb stick? if so how was the iso written to usb? dd works best
>> in my experience.
>>
>> --
>> Alastair Munro
>>
>>
>> -----Original Message-----
>> From: Tony Schreiner <anthony.schreiner(a)bc.edu>
>> To: cobbler mailing list <cobbler(a)lists.fedorahosted.org>
>> Sent: Wed, 25 May 2016 20:45
>> Subject: [cobbler] cobbler managing debian install no CD-ROM detected
>>
>> Have been managing CentOS system with cobbler for a while, and decided to
>> try to add Debian to the mix.
>>
>> I loop mounted the firmware-8.4.0-amd64-netinst.iso image, which is
>> current Jessie netinst + non-free firmware, and ran import as
>>
>> # cobbler import --name=jessie --breed=debian --os-version=jessie
>> --path=/mnt
>>
>> task started: 2016-05-25_144840_import
>> task started (id=Media import, time=Wed May 25 14:48:40 2016)
>> Found a candidate signature: breed=debian, version=jessie
>>
>> running: /usr/bin/file
>> /var/www/cobbler/ks_mirror/jessie/dists/jessie/Release
>> received on stdout:
>> /var/www/cobbler/ks_mirror/jessie/dists/jessie/Release: ASCII text
>>
>> received on stderr:
>> Found a matching signature: breed=debian, version=jessie
>> Adding distros from path /var/www/cobbler/ks_mirror/jessie:
>> creating new distro: jessie-x86_64
>> trying symlink: /var/www/cobbler/ks_mirror/jessie ->
>> /var/www/cobbler/links/jessie-x86_64
>> creating new profile: jessie-x86_64
>> creating new distro: jessie-gtk-x86_64
>> trying symlink: /var/www/cobbler/ks_mirror/jessie ->
>> /var/www/cobbler/links/jessie-gtk-x86_64
>> creating new profile: jessie-gtk-x86_64
>> creating new distro: jessie-xen-x86_64
>> trying symlink: /var/www/cobbler/ks_mirror/jessie ->
>> /var/www/cobbler/links/jessie-xen-x86_64
>> creating new profile: jessie-xen-x86_64
>> associating repos
>> checking for apt repo(s)
>> adding apt repo for jessie-x86_64
>> Added repos for jessie-x86_64
>> adding apt repo for jessie-gtk-x86_64
>> Added repos for jessie-gtk-x86_64
>> adding apt repo for jessie-xen-x86_64
>> Added repos for jessie-xen-x86_64
>> *** TASK COMPLETE ***
>>
>> looks pretty normal.
>> I have created a sub-profile based on jessie-x86_64 called
>> jessie-precision670 (old dell workstation), but the only difference is the
>> assignment of preseed file slightly modified from sample.seed as the
>> kickstart. Then I assigned this profile to a system.
>>
>> When the system installs, during the hardware discovery, it shows:
>>
>> No common CD-ROM drive was detected.
>>
>> ...
>>
>> and I cannot proceed. This seems to be before network detection takes
>> place.
>> I first tried with the regular debian-8.4.0-amd64.iso image; the network
>> driver is e1000.
>>
>> Any suggestions?
>>
>> Tony S
>>
>
>
7 years, 10 months
cobbler managing debian install no CD-ROM detected
by Tony Schreiner
Have been managing CentOS system with cobbler for a while, and decided to
try to add Debian to the mix.
I loop mounted the firmware-8.4.0-amd64-netinst.iso image, which is current
Jessie netinst + non-free firmware, and ran import as
# cobbler import --name=jessie --breed=debian --os-version=jessie
--path=/mnt
task started: 2016-05-25_144840_import
task started (id=Media import, time=Wed May 25 14:48:40 2016)
Found a candidate signature: breed=debian, version=jessie
running: /usr/bin/file
/var/www/cobbler/ks_mirror/jessie/dists/jessie/Release
received on stdout: /var/www/cobbler/ks_mirror/jessie/dists/jessie/Release:
ASCII text
received on stderr:
Found a matching signature: breed=debian, version=jessie
Adding distros from path /var/www/cobbler/ks_mirror/jessie:
creating new distro: jessie-x86_64
trying symlink: /var/www/cobbler/ks_mirror/jessie ->
/var/www/cobbler/links/jessie-x86_64
creating new profile: jessie-x86_64
creating new distro: jessie-gtk-x86_64
trying symlink: /var/www/cobbler/ks_mirror/jessie ->
/var/www/cobbler/links/jessie-gtk-x86_64
creating new profile: jessie-gtk-x86_64
creating new distro: jessie-xen-x86_64
trying symlink: /var/www/cobbler/ks_mirror/jessie ->
/var/www/cobbler/links/jessie-xen-x86_64
creating new profile: jessie-xen-x86_64
associating repos
checking for apt repo(s)
adding apt repo for jessie-x86_64
Added repos for jessie-x86_64
adding apt repo for jessie-gtk-x86_64
Added repos for jessie-gtk-x86_64
adding apt repo for jessie-xen-x86_64
Added repos for jessie-xen-x86_64
*** TASK COMPLETE ***
looks pretty normal.
I have created a sub-profile based on jessie-x86_64 called
jessie-precision670 (old dell workstation), but the only difference is the
assignment of preseed file slightly modified from sample.seed as the
kickstart. Then I assigned this profile to a system.
When the system installs, during the hardware discovery, it shows:
No common CD-ROM drive was detected.
...
and I cannot proceed. This seems to be before network detection takes place.
I first tried with the regular debian-8.4.0-amd64.iso image; the network
driver is e1000.
Any suggestions?
Tony S
7 years, 11 months
Cobbler service unable to start on rhel6.4 after restarting
by Kishore Kiran
[kkishore@xxxxxxx]$ rpm -qa | grep cobbler
cobbler-2.4.0-1.el6.noarch
cobbler-web-2.4.0-1.el6.noarch
[kkishore@xxxxxxx]$ python --version
Python 2.6.6
[kkishore@xxxxxxx]$ more /etc/redhat-release
Red Hat Enterprise Linux Server release 6.4 (Santiago)
[kkishore@xxxxxxx]$ sudo service cobblerd restart
Stopping cobbler daemon: [FAILED]
Starting cobbler daemon: Traceback (most recent call last):
File "/usr/bin/cobblerd", line 77, in main
api = cobbler_api.BootAPI(is_cobblerd=True)
File "/usr/lib/python2.6/site-packages/cobbler/api.py", line 134, in __init__
self.deserialize()
File "/usr/lib/python2.6/site-packages/cobbler/api.py", line 956, in deserialize
return self._config.deserialize()
File "/usr/lib/python2.6/site-packages/cobbler/config.py", line 266, in deserialize
raise CX("serializer: error loading collection %s. Check /etc/cobbler/modules.conf" % item.collection_type())
CX: 'serializer: error loading collection profile. Check /etc/cobbler/modules.conf'
[ OK ]
[kkishore@xxxxxxx]$ sudo service cobblerd status
cobblerd dead but subsys locked
7 years, 11 months
Documentation on new mgmt_classes fields
by Pezzarossi, Gianni
Hey guys, So while setting up a new cobbler server (2.6.11) I was adding in some management classes and noticed that since the last version we had running (2.2.2), the web management fields have changed.
2.2.2 only had fields for: Name, Owners, Comment, Packages, and Files.
2.6.11 now has those same fields, plus: Class Name, Is Definition?, Parameters/Variables
However I can't find anything that says where/if these fields are used? Like what is the difference between Name, and Class Name fields?
We use the management classes to export to ansible for config management, and they show up as expected if we just populate the name field. But I'm just curious as to what the function of the rest is.
Thanks,
-------------------------------------
Gianni Pezzarossi
Linux Systems Administrator
User Services:Research
Engineering IT Shared Services
University of Illinois @ Urbana-Champaign
(217)244-7549
270 Materials Research Laboratory
engrit-help(a)illinois.edu<https://webmail.illinois.edu/owa/redir.aspx?C=e74d600e17004202a76c2e7068e...>
7 years, 11 months
