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, 6 months
Cobbler on CentOS 7
by Harry Hoffman
Hi All,
Wondering if anyone is running cobblerd on CentOS 7? It seems that the
debmirror package isn't available and running cobbler check doesn't seem
to know what distribution it's running on, can't check httpd (even
though it's in the path
2 : Unknown distribution type, cannot check for running service cobblerd
3 : file /etc/xinetd.d/rsync does not exist
4 : Apache (httpd) is not installed and/or in path
5 : debmirror package is not installed, it will be required to manage
debian deployments and repositories
Thoughts?
Cheers,
Harry
8 years, 9 months
Changes in kickstart file do not take effect in Cobbler.
by Gi Dot
I am using Cobbler to install SLES 11 SP2 and it has been running fine all
the while. Recently I modified the kickstart file by changing the size of
the root partition from 18GB to 36GB. To my surprise the modification did
not take place - Cobbler created a root partition with the size of 18GB. I
tried removing the profile, renaming it, but no success.
I am completely stump as to where Cobbler is getting the value 18GB from.
Is there some kind of cache that is keeping the old kickstart file
somewhere and I need to clear that up first?
The part where I did the modification:
<partition>
<create config:type="boolean">true</create>
<crypt_fs config:type="boolean">false</crypt_fs>
<filesystem config:type="symbol">ext3</filesystem>
<format config:type="boolean">true</format>
<fstopt>acl,user_xattr</fstopt>
<loop_fs config:type="boolean">false</loop_fs>
<lv_name>lvroot</lv_name>
<mount>/</mount>
<mountby config:type="symbol">device</mountby>
<partition_id config:type="integer">131</partition_id>
<raid_options/>
<resize config:type="boolean">false</resize>
<size>36GB</size>
</partition>
Any help is appreciated.
Thanks.
8 years, 10 months
Re: [cobbler] Ilo baremetal
by Alan Evangelista
On 04/01/2015 10:52 PM, Sethuraman, Murali wrote:
> Hi Alan,
> Thanks for your continued responses. When "dhclient" is executed without any options from the baremetal, /var/log/messages on the cobbler server does not get updated with any DHCP requests [similar to what happens when it tries to pxe boot]. It does not work.
I know I have already asked again, but just confirming
- Are you sure the DHCP server is in the same subnet of the client?
- Are you sure there are no other DHCP servers in the same subnet?
If both answers are "yes", there is something odd in your network/DHCP
setup which prevents
broadcasted DHCP requests to arrive in the DHCP server. I'd also check
if there are any link layer firewalls
which may be blocking the communication. If not, I'd use some network
debugging tool such
as tcpdump in another system of the same subnet and assert if it is
receiving the broadcasted DHCP
requests (UDP packages), then we know if the problem is specific to the
DHCP server or not.
Regards,
Alan Evangelista
8 years, 10 months
Provisioning 50 cluster nodes
by Jagga Soorma
Hi Guys,
I have been using cobbler for a few months now and it has worked very
well for us. However, we have been only building a few servers at a
time and my current process of having our SA's run a "cobbler system
add" command for each server has worked just fine. I now have a
requirement to build a cluster with 50+ nodes and was wondering how to
automate this as much as possible. Has anyone out there already done
something similar? If so, how did you approach this? I would hate to
tell someone to run the cobbler system add command for 50 servers.
Thanks in advance for your help with this!
Regards.
8 years, 10 months
synchronizing cobbler installations
by Jeremy Mordkoff
Hi all,
I have a need to synchronize the content and config between multiple instances of cobbler. Each instance is running in a VM and new instances are created by cloning the VM image. These instances are spread around geographically and some do not have very fast internet connections.
For config, I have /var/lib/cobbler and /etc/cobbler in source control. I commit my changes on the master instance and then update on all of the slave instances and then restart cobbler. Seems to work well and my git repo is already accessible over the internet so this is convenient.
But I am not so keen on putting my repo mirrors in source control because they are large. Plus I have a pip wheelhouse and an NPM proxy cache.
Any suggestions on how to keep these all in sync? I am considering just using rsync, but that will require moving my master instance (or a copy thereof) someplace accessible by all.
I guess this isn't a cobbler question at all, but perhaps someone has some insights that might help me.
Thanks
---
Jeremy Mordkoff
RIFT.io
77 S Bedford St, Burlington, MA 01803
8 years, 11 months
Re: [cobbler] cobbler Digest, Vol 82, Issue 11
by Robin Casset
CDT
Robin CASSET
Service R&D
Bull SAS
________________________________________
From: cobbler-bounces(a)lists.fedorahosted.org [cobbler-bounces(a)lists.fedorahosted.org] on behalf of cobbler-request(a)lists.fedorahosted.org [cobbler-request(a)lists.fedorahosted.org]
Sent: Wednesday, April 29, 2015 6:27 AM
To: cobbler(a)lists.fedorahosted.org
Subject: cobbler Digest, Vol 82, Issue 11
Send cobbler mailing list submissions to
cobbler(a)lists.fedorahosted.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.fedorahosted.org/mailman/listinfo/cobbler
or, via email, send a message with subject or body 'help' to
cobbler-request(a)lists.fedorahosted.org
You can reach the person managing the list at
cobbler-owner(a)lists.fedorahosted.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cobbler digest..."
Today's Topics:
1. Re: Unamble to install nodes with Cobbler (Harry Hoffman)
2. Web doc issue (Orion Poplawski)
3. Re: Web doc issue (Alan Evangelista)
4. Provisioning 50 cluster nodes (Jagga Soorma)
5. Re: Provisioning 50 cluster nodes (Alan Evangelista)
6. Re: Provisioning 50 cluster nodes (Jagga Soorma)
7. Re: Provisioning 50 cluster nodes (Alan Evangelista)
----------------------------------------------------------------------
Message: 1
Date: Mon, 27 Apr 2015 08:13:55 -0400
From: Harry Hoffman <hhoffman(a)ip-solutions.net>
To: cobbler mailing list <cobbler(a)lists.fedorahosted.org>
Subject: Re: [cobbler] Unamble to install nodes with Cobbler
Message-ID: <97a7a7f8-616e-4754-b22a-67b7cb709395(a)email.android.com>
Content-Type: text/plain; charset=utf-8
Hi Robin,
Are you sure the tftp-server is listening and there's not a firewall (host or network based that's blocking communication to that tftp port)?
Does the client system get a dhcp address from the server?
Cheers,
Harry
On Apr 27, 2015 3:20 AM, Robin Casset <robin.casset(a)atos.net> wrote:
>
> Hello,
>
> My name is Robin, I'm an apprentice engineer at Bull SAS.
> I recently install cobbler on a server to make some few test of it. I have been able to import an iso, create a repo and set up profiles. The pxe file is generated and seems to be good but when the node boot on the network I have a message "unable to find files"
>
> here are my node and image profiles :
>
> Name : dep12
> TFTP Boot Files : {}
> Comment :
> Enable gPXE? : False
> Fetchable Files : {}
> Gateway : 192.168.1.0
> Hostname : dep12
> Image :
> IPv6 Autoconfiguration : False
> IPv6 Default Device :
> Kernel Options : {}
> Kernel Options (Post Install) : {}
> Kickstart : /var/lib/cobbler/kickstarts/dep12.ks
> Kickstart Metadata : {}
> LDAP Enabled : False
> LDAP Management Type : authconfig
> Management Classes : []
> Management Parameters : <<inherit>>
> Monit Enabled : False
> Name Servers : ['192.168.1.1']
> Name Servers Search Path : []
> Netboot Enabled : True
> Owners : ['root']
> Power Management Address : 192.168.1.13
> Power Management ID :
> Power Management Password : administrator-
> Power Management Type : apc
> Power Management Username : administrator
> Profile : Centos7-x86_64
> Internal proxy : <<inherit>>
> Red Hat Management Key : <<inherit>>
> Red Hat Management Server : <<inherit>>
> Repos Enabled : False
> Server Override : <<inherit>>
> Status : production
> Template Files : {}
> Virt Auto Boot : 0
> Virt CPUs : <<inherit>>
> Virt Disk Driver Type : <<inherit>>
> Virt File Size(GB) : <<inherit>>
> Virt Path : <<inherit>>
> Virt PXE Boot : 0
> Virt RAM (MB) : <<inherit>>
> Virt Type : xenpv
> Interface ===== : eth0
> Bonding Opts :
> Bridge Opts :
> CNAMES : []
> DHCP Tag : default
> DNS Name :
> Per-Interface Gateway : 192.168.1.0
> Master Interface :
> Interface Type :
> IP Address : 192.168.1.12
> IPv6 Address :
> IPv6 Default Gateway :
> IPv6 MTU :
> IPv6 Prefix :
> IPv6 Secondaries : []
> IPv6 Static Routes : []
> MAC Address : 00:30:48:7a:3c:bc
> Management Interface : True
> MTU :
> Subnet Mask : 255.255.255.0
> Static : True
> Static Routes : []
> Virt Bridge : xenbr0
>
> profiles:
> ==========
> Name : Centos7-x86_64
> TFTP Boot Files : {}
> Comment :
> DHCP Tag : linux
> Distribution : Centos7-x86_64
> Enable gPXE? : False
> Enable PXE Menu? : True
> Fetchable Files : {}
> Kernel Options : {}
> Kernel Options (Post Install) : {}
> Kickstart : /var/lib/cobbler/kickstarts/dep12.ks
> Kickstart Metadata : {}
> Management Classes : []
> Management Parameters : <<inherit>>
> Name Servers : []
> Name Servers Search Path : []
> Owners : ['root']
> Parent Profile :
> Internal proxy :
> Red Hat Management Key : <<inherit>>
> Red Hat Management Server : <<inherit>>
> Repos : ['Centos7']
> Server Override : <<inherit>>
> Template Files : {}
> Virt Auto Boot : 1
> Virt Bridge : xenbr0
> Virt CPUs : 1
> Virt Disk Driver Type : raw
> Virt File Size(GB) : 5
> Virt Path :
> Virt RAM (MB) : 512
> Virt Type : kvm
>
> And here the pxe file:
>
> default linux
> prompt 0
> timeout 1
> label linux
> kernel /images/Centos7-x86_64/vmlinuz
> ipappend 2
> append initrd=/images/Centos7-x86_64/initrd.img ksdevice=bootif lang= kssendmac text ks=http://192.168.1.1/cblr/svc/op/ks/system/dep12
>
> I can't see where is the mistake and I tried many options...
>
> Thank's for you help!
>
> best regards
>
>
> CDT
>
> Robin CASSET
> Service R&D
> Bull SAS
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/cobbler
------------------------------
Message: 2
Date: Mon, 27 Apr 2015 15:36:28 -0600
From: Orion Poplawski <orion(a)cora.nwra.com>
To: cobbler mailing list <cobbler(a)lists.fedorahosted.org>
Subject: [cobbler] Web doc issue
Message-ID: <553EABDC.5050002(a)cora.nwra.com>
Content-Type: text/plain; charset=utf-8
http://www.cobblerd.org/manuals/2.6.0/3/5_-_Kickstart_Templating.html
mentions using a kickstart template in /opt, which is no longer allowed.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301 http://www.nwra.com
------------------------------
Message: 3
Date: Mon, 27 Apr 2015 18:48:52 -0300
From: Alan Evangelista <alanoe(a)linux.vnet.ibm.com>
To: cobbler(a)lists.fedorahosted.org
Subject: Re: [cobbler] Web doc issue
Message-ID: <553EAEC4.3040300(a)linux.vnet.ibm.com>
Content-Type: text/plain; charset=utf-8; format=flowed
On 04/27/2015 06:36 PM, Orion Poplawski wrote:
> http://www.cobblerd.org/manuals/2.6.0/3/5_-_Kickstart_Templating.html
>
> mentions using a kickstart template in /opt, which is no longer allowed.
Opened an issue in Cobbler issue tracker:
https://github.com/cobbler/cobbler/issues/1455
Thanks for reporting.
Regards,
Alan Evangelista
------------------------------
Message: 4
Date: Tue, 28 Apr 2015 20:51:13 -0700
From: Jagga Soorma <jagga13(a)gmail.com>
To: cobbler mailing list <cobbler(a)lists.fedorahosted.org>
Subject: [cobbler] Provisioning 50 cluster nodes
Message-ID:
<CAKyjK50amjpr9cgMe3M9-JfDgEb=Ax2RJZ9oOVeKnY_qrHp1zg(a)mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Hi Guys,
I have been using cobbler for a few months now and it has worked very
well for us. However, we have been only building a few servers at a
time and my current process of having our SA's run a "cobbler system
add" command for each server has worked just fine. I now have a
requirement to build a cluster with 50+ nodes and was wondering how to
automate this as much as possible. Has anyone out there already done
something similar? If so, how did you approach this? I would hate to
tell someone to run the cobbler system add command for 50 servers.
Thanks in advance for your help with this!
Regards.
------------------------------
Message: 5
Date: Wed, 29 Apr 2015 00:57:09 -0300
From: Alan Evangelista <alanoe(a)linux.vnet.ibm.com>
To: cobbler(a)lists.fedorahosted.org
Subject: Re: [cobbler] Provisioning 50 cluster nodes
Message-ID: <55405695.3000807(a)linux.vnet.ibm.com>
Content-Type: text/plain; charset=utf-8; format=flowed
On 04/29/2015 12:51 AM, Jagga Soorma wrote:
> I now have a
> requirement to build a cluster with 50+ nodes and was wondering how to
> automate this as much as possible. Has anyone out there already done
> something similar? If so, how did you approach this? I would hate to
> tell someone to run the cobbler system add command for 50 servers.
I suppose you have a list of the MAC addresses and power management data
(and maybe
IP addresses) of the 50+ nodes. Simply create a Python script which
creates the missing
system data (eg name) automatically and uses Cobbler CLI / XML-RPC
interface to add the
systems to Cobbler.
Regards,
Alan Evangelista
------------------------------
Message: 6
Date: Tue, 28 Apr 2015 21:11:30 -0700
From: Jagga Soorma <jagga13(a)gmail.com>
To: cobbler mailing list <cobbler(a)lists.fedorahosted.org>
Subject: Re: [cobbler] Provisioning 50 cluster nodes
Message-ID:
<CAKyjK536x99ZQFFBUOgCvwq16T7iqNRAT0=hkNufCODbGP0O-w(a)mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Actually I don't have the mac addresses handy. Would have to login to
the ilo/idrac of each server and grab the mac which is very time
consuming. I do have all the hostnames and ip addresses defined in
dns. Is there a way for me to get the bare metal hardware to tell the
cobbler server its mac addresses and auto register somehow. From
there maybe I can write a shell script to populate the other needed
info.
Thanks.
On Tue, Apr 28, 2015 at 8:57 PM, Alan Evangelista
<alanoe(a)linux.vnet.ibm.com> wrote:
> On 04/29/2015 12:51 AM, Jagga Soorma wrote:
>>
>> I now have a
>> requirement to build a cluster with 50+ nodes and was wondering how to
>> automate this as much as possible. Has anyone out there already done
>> something similar? If so, how did you approach this? I would hate to
>> tell someone to run the cobbler system add command for 50 servers.
>
>
> I suppose you have a list of the MAC addresses and power management data
> (and maybe
> IP addresses) of the 50+ nodes. Simply create a Python script which creates
> the missing
> system data (eg name) automatically and uses Cobbler CLI / XML-RPC interface
> to add the
> systems to Cobbler.
>
>
> Regards,
> Alan Evangelista
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/cobbler
Hi!
Yes, all dhcp/dns/tftp parameters were ok.
I juste succed in depoyling nodes, the problem was the path of the repos...
Thank's and sorry for asking your help for that ><
best regards
Robin
------------------------------
Message: 7
Date: Wed, 29 Apr 2015 01:27:45 -0300
From: Alan Evangelista <alanoe(a)linux.vnet.ibm.com>
To: cobbler(a)lists.fedorahosted.org
Subject: Re: [cobbler] Provisioning 50 cluster nodes
Message-ID: <55405DC1.3000503(a)linux.vnet.ibm.com>
Content-Type: text/plain; charset=utf-8; format=flowed
On 04/29/2015 01:11 AM, Jagga Soorma wrote:
> Actually I don't have the mac addresses handy. Would have to login to
> the ilo/idrac of each server and grab the mac which is very time
> consuming.
Write a script to do that? expect/pexpect may be helpful.
> I do have all the hostnames and ip addresses defined in
> dns. Is there a way for me to get the bare metal hardware to tell the
> cobbler server its mac addresses and auto register somehow.
If your bare metal hardware is in the same LAN of the Cobbler server,
you can use "arp -a"
after pinging the bare metal hardware from Cobbler server to get its MAC
address.
If Cobbler server is not in the same LAN, you could split this in 2
steps: run a MAC address
discovery script in a system which *is* in the same LAN of the bare
metal hardware and then
add the systems to Cobbler.
Regards,
Alan Evangelista
------------------------------
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
End of cobbler Digest, Vol 82, Issue 11
***************************************
8 years, 11 months
Unamble to install nodes with Cobbler
by Robin Casset
Hello,
My name is Robin, I'm an apprentice engineer at Bull SAS.
I recently install cobbler on a server to make some few test of it. I have been able to import an iso, create a repo and set up profiles. The pxe file is generated and seems to be good but when the node boot on the network I have a message "unable to find files"
here are my node and image profiles :
Name : dep12
TFTP Boot Files : {}
Comment :
Enable gPXE? : False
Fetchable Files : {}
Gateway : 192.168.1.0
Hostname : dep12
Image :
IPv6 Autoconfiguration : False
IPv6 Default Device :
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart : /var/lib/cobbler/kickstarts/dep12.ks
Kickstart Metadata : {}
LDAP Enabled : False
LDAP Management Type : authconfig
Management Classes : []
Management Parameters : <<inherit>>
Monit Enabled : False
Name Servers : ['192.168.1.1']
Name Servers Search Path : []
Netboot Enabled : True
Owners : ['root']
Power Management Address : 192.168.1.13
Power Management ID :
Power Management Password : administrator-
Power Management Type : apc
Power Management Username : administrator
Profile : Centos7-x86_64
Internal proxy : <<inherit>>
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Repos Enabled : False
Server Override : <<inherit>>
Status : production
Template Files : {}
Virt Auto Boot : 0
Virt CPUs : <<inherit>>
Virt Disk Driver Type : <<inherit>>
Virt File Size(GB) : <<inherit>>
Virt Path : <<inherit>>
Virt PXE Boot : 0
Virt RAM (MB) : <<inherit>>
Virt Type : xenpv
Interface ===== : eth0
Bonding Opts :
Bridge Opts :
CNAMES : []
DHCP Tag : default
DNS Name :
Per-Interface Gateway : 192.168.1.0
Master Interface :
Interface Type :
IP Address : 192.168.1.12
IPv6 Address :
IPv6 Default Gateway :
IPv6 MTU :
IPv6 Prefix :
IPv6 Secondaries : []
IPv6 Static Routes : []
MAC Address : 00:30:48:7a:3c:bc
Management Interface : True
MTU :
Subnet Mask : 255.255.255.0
Static : True
Static Routes : []
Virt Bridge : xenbr0
profiles:
==========
Name : Centos7-x86_64
TFTP Boot Files : {}
Comment :
DHCP Tag : linux
Distribution : Centos7-x86_64
Enable gPXE? : False
Enable PXE Menu? : True
Fetchable Files : {}
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart : /var/lib/cobbler/kickstarts/dep12.ks
Kickstart Metadata : {}
Management Classes : []
Management Parameters : <<inherit>>
Name Servers : []
Name Servers Search Path : []
Owners : ['root']
Parent Profile :
Internal proxy :
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Repos : ['Centos7']
Server Override : <<inherit>>
Template Files : {}
Virt Auto Boot : 1
Virt Bridge : xenbr0
Virt CPUs : 1
Virt Disk Driver Type : raw
Virt File Size(GB) : 5
Virt Path :
Virt RAM (MB) : 512
Virt Type : kvm
And here the pxe file:
default linux
prompt 0
timeout 1
label linux
kernel /images/Centos7-x86_64/vmlinuz
ipappend 2
append initrd=/images/Centos7-x86_64/initrd.img ksdevice=bootif lang= kssendmac text ks=http://192.168.1.1/cblr/svc/op/ks/system/dep12
I can't see where is the mistake and I tried many options...
Thank's for you help!
best regards
CDT
Robin CASSET
Service R&D
Bull SAS
8 years, 11 months
Cobbler System Network Configuration
by Hrishikesh
Hi All,
I am building an RHEL 7 instance using cobbler.
I am facing a problem related to network configuration for a system
defined in cobbler web interface.
I have defined an interface named eth0 in cobbler web interface for the
system.
When I build using koan, it creates 2 interfaces with names eth0 and
ensXX. And the ip address for both is same and is the one that mentioned
in cobbler web interface for eth0.
Any idea how to restrict the creation of ensXX interface ?
Thanks,
Hrishikesh
8 years, 11 months