VMware EFI + CentOS7
by Marcq, Nicolas
Hi experts !
I'm testing Cobbler and I'm stuck when I try to deploy CentOS 7 on VMware VM (ESX 5.5) with EFI bios activated.
I don't see anything about specific configuration I should have added on the official documentation. In DHCP log I can see the requested boot file is pxelinux.0 instead of grub-x86_64.efi but I don't know why.
Thx for any help!
My Cobbler version
cobbler --version
Cobbler 2.6.9
source: ?, ?
build time: Mon Jun 22 18:06:11 2015
This is my DCHP config
subnet 192.168.0.0 netmask 255.255.255.0 {
option routers 192.168.0.1;
option domain-name-servers 16.110.135.51;
option subnet-mask 255.255.255.0;
range dynamic-bootp 192.168.0.100 192.168.0.200;
default-lease-time 21600;
max-lease-time 43200;
next-server 192.168.0.1;
class "pxeclients" {
match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
if option pxe-system-type = 00:02 {
filename "ia64/elilo.efi";
} else if option pxe-system-type = 00:06 {
filename "grub/grub-x86.efi";
} else if option pxe-system-type = 00:07 {
filename "grub/grub-x86_64.efi";
} else {
filename "pxelinux.0";
}
}
}
My System declaration
cat /var/lib/tftpboot/grub/01-00-50-56-BD-48-E7
title CentOS-7-x86_64
root (nd)
kernel /images/CentOS-7-x86_64/vmlinuz ksdevice=bootif lang= kssendmac text ks=http://192.168.0.1/cblr/svc/op/ks/system/test
initrd /images/CentOS-7-x86_64/initrd.img
My DHCP log
tail -f /var/log/messages
Aug 3 15:14:43 hwosvm12 dhcpd:
Aug 3 15:14:43 hwosvm12 dhcpd: Sending on Socket/fallback/fallback-net
Aug 3 15:14:43 hwosvm12 systemd: Started DHCPv4 Server Daemon.
Aug 3 15:14:57 hwosvm12 dhcpd: DHCPDISCOVER from 00:50:56:bd:48:e7 via ens224
Aug 3 15:14:58 hwosvm12 dhcpd: DHCPOFFER on 192.168.0.101 to 00:50:56:bd:48:e7 via ens224
Aug 3 15:15:00 hwosvm12 dhcpd: DHCPREQUEST for 192.168.0.101 (192.168.0.1) from 00:50:56:bd:48:e7 via ens224
Aug 3 15:15:00 hwosvm12 dhcpd: DHCPACK on 192.168.0.101 to 00:50:56:bd:48:e7 via ens224
Aug 3 15:15:00 hwosvm12 in.tftpd[23148]: RRQ from 192.168.0.101 filename /pxelinux.0
Aug 3 15:15:00 hwosvm12 in.tftpd[23148]: tftp: client does not accept options
Aug 3 15:15:00 hwosvm12 in.tftpd[23149]: RRQ from 192.168.0.101 filename /pxelinux.0
Aug 3 15:30:01 hwosvm12 xinetd[13037]: EXIT: tftp status=0 pid=22585 duration=1699(sec)
8 years, 6 months
Re: [cobbler] CentOS 7 install failure
by Chris Johnson
Hi,
Don't know if this last post made it.
I've narrowed it down to something in the network_config, pre and post
SNIPPETS. I have seen bug report 1117640 however no data is missing as
in that case, I've done a cobbler system getks and all the data is
there as far as I can tell. I pulled all three SNIPPETs out and
replaced them with the proper network kickstart line and the error about
an illegal IP address string is gone. The install has other issues but
that's not this problem.
So it's something in the network SNIPPETs that is causing the illegal IP
address string error when trying to install CentOS 7.
Chris J.
> Hi.
>
> I've probably missed something somewhere. I'd love to know what.
>
> I have a cobbler server (2.6.5-9.1) running on CentOS 6.5 in a VBox
> (4.3.16) VM on OS X (10.9.5). Now 6.5 installs just fine this way on
> my other VMs. However when trying to install C7, anaconda keeps
> dumping on an illegal IP address string passed to inet_aton and that's
> even using the default sample.ks kickstart.
>
> Has anyone managed to install CentOS 7 on a VBox VM? I'd love to know
> where this error is coming from.
>
> Tnx.
>
> Chris J.
>
>
8 years, 7 months
Cobbler authorization with LDAP
by Kyle Flavin
I've set up a test Cobbler server to explore its permissions system. I need to be able to allow different groups to have access to cobbler through the WebUI, but only give them rights to change/create objects they own.
It looks like I can do this with a combination of the authn_ldap + authz_ownership modules: https://fedorahosted.org/cobbler/wiki/CustomizableAuthorization
Using the docs, I was able to setup the Cobbler LDAP authentication on my server, but it doesn't look like I can use LDAP groups within /etc/cobbler/users.conf. Instead, I have to specify the actual username like this:
[admin]
admin = ""
cobbler = ""
myuser = ""
I'd like to be able to add an LDAP group as follows:
[admin]
admin = ""
cobbler = ""
mygroup = ""
So I don't have to update user groups in two different places (LDAP and Cobbler).
Is that supported in some other way?
Thanks,
Kyle
8 years, 8 months
Ipmitool and ipmilan woes and power resetting and PXE Mode issues.
by Jennifer Patrick
Just having some woes with making fence_ipmilan work with some Supermicro
servers (Don't say use the supermicro IPMI Tool, we're trying to get around
that.)
The problem is, using fence_ipmilan, we can initiate a boot (off then on)
from the web GUI, or from the CLI via...
*# cobbler system reboot --name=test123*
*task started: 2015-08-05_092815_power*
*task started (id=Power management (reboot), time=Wed Aug 5 09:28:15 2015)*
*cobbler power configuration is:*
* type : ipmilan*
* address: 192.168.1.5*
* user : user*
* id :*
*running: /usr/sbin/fence_ipmilan*
*running: /usr/sbin/fence_ipmilan*
*received on stdout: Powering off machine @ IPMI:**192.168.1.5**...Failed*
*received on stderr:*
*running: /usr/sbin/fence_ipmilan*
*received on stdout: Powering off machine @ IPMI:**192.168.1.5**...Done*
*received on stderr:*
*cobbler power configuration is:*
* type : ipmilan*
* address: **192.168.1.5*
* user : user*
* id :*
*running: /usr/sbin/fence_ipmilan*
*received on stdout: Powering on machine @ IPMI:**192.168.1.5**...Failed*
*received on stderr: ipmilan: Power still off*
*running: /usr/sbin/fence_ipmilan*
*received on stdout: Powering on machine @ IPMI:192.168.1.5...Done*
*received on stderr:*
**** TASK COMPLETE ****
So that's great. My real question comes from the fact that I can't make
cobbler set these machines to reboot via the Web GUI to Netboot/PXE. It
just seems to never issue the right command via fence_ipmilan (which
actually uses IPMITOOL)
I can do it fine in IPMITOOL:
*ipmitool -H 192.168.1.5 -U user -I lanplus -P password chassis bootdev
pxeipmitool -H 192.168.1.5 -U user -I lanplus -P password chassis power
reset*
And the system reboots into PXE boot mode.
So is there something I have to mangle in
/etc/cobbler/fence_ipmilan.template?
Something Else?
All help is appreciated.
Thanks.
JLP
8 years, 8 months
Re: [cobbler] VMware EFI + CentOS7
by Marcq, Nicolas
Hi !
To resolv this problem I have had to add the section that deals with the pxeclients class into the group section of the DHCP template.
I've replaced the condition that load the net bios file under the "group" section:
filename "$iface.filename";
By these lines
#filename "$iface.filename";
class "pxeclients" {
match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
if option pxe-system-type = 00:02 {
filename "ia64/elilo.efi";
} else if option pxe-system-type = 00:06 {
filename "grub/grub-x86.efi";
} else if option pxe-system-type = 00:07 {
filename "grub/grub-x86_64.efi";
} else {
filename "pxelinux.0";
}
}
That's it.
De : Marcq, Nicolas
Envoyé : lundi 3 août 2015 15:40
À : 'cobbler(a)lists.fedorahosted.org' <cobbler(a)lists.fedorahosted.org>
Objet : VMware EFI + CentOS7
Hi experts !
I'm testing Cobbler and I'm stuck when I try to deploy CentOS 7 on VMware VM (ESX 5.5) with EFI bios activated.
I don't see anything about specific configuration I should have added on the official documentation. In DHCP log I can see the requested boot file is pxelinux.0 instead of grub-x86_64.efi but I don't know why.
Thx for any help!
My Cobbler version
cobbler --version
Cobbler 2.6.9
source: ?, ?
build time: Mon Jun 22 18:06:11 2015
This is my DCHP config
subnet 192.168.0.0 netmask 255.255.255.0 {
option routers 192.168.0.1;
option domain-name-servers 16.110.135.51;
option subnet-mask 255.255.255.0;
range dynamic-bootp 192.168.0.100 192.168.0.200;
default-lease-time 21600;
max-lease-time 43200;
next-server 192.168.0.1;
class "pxeclients" {
match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
if option pxe-system-type = 00:02 {
filename "ia64/elilo.efi";
} else if option pxe-system-type = 00:06 {
filename "grub/grub-x86.efi";
} else if option pxe-system-type = 00:07 {
filename "grub/grub-x86_64.efi";
} else {
filename "pxelinux.0";
}
}
}
My System declaration
cat /var/lib/tftpboot/grub/01-00-50-56-BD-48-E7
title CentOS-7-x86_64
root (nd)
kernel /images/CentOS-7-x86_64/vmlinuz ksdevice=bootif lang= kssendmac text ks=http://192.168.0.1/cblr/svc/op/ks/system/test
initrd /images/CentOS-7-x86_64/initrd.img
My DHCP log
tail -f /var/log/messages
Aug 3 15:14:43 hwosvm12 dhcpd:
Aug 3 15:14:43 hwosvm12 dhcpd: Sending on Socket/fallback/fallback-net
Aug 3 15:14:43 hwosvm12 systemd: Started DHCPv4 Server Daemon.
Aug 3 15:14:57 hwosvm12 dhcpd: DHCPDISCOVER from 00:50:56:bd:48:e7 via ens224
Aug 3 15:14:58 hwosvm12 dhcpd: DHCPOFFER on 192.168.0.101 to 00:50:56:bd:48:e7 via ens224
Aug 3 15:15:00 hwosvm12 dhcpd: DHCPREQUEST for 192.168.0.101 (192.168.0.1) from 00:50:56:bd:48:e7 via ens224
Aug 3 15:15:00 hwosvm12 dhcpd: DHCPACK on 192.168.0.101 to 00:50:56:bd:48:e7 via ens224
Aug 3 15:15:00 hwosvm12 in.tftpd[23148]: RRQ from 192.168.0.101 filename /pxelinux.0
Aug 3 15:15:00 hwosvm12 in.tftpd[23148]: tftp: client does not accept options
Aug 3 15:15:00 hwosvm12 in.tftpd[23149]: RRQ from 192.168.0.101 filename /pxelinux.0
Aug 3 15:30:01 hwosvm12 xinetd[13037]: EXIT: tftp status=0 pid=22585 duration=1699(sec)
8 years, 8 months
