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 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, 10 months
cobbler import fedora 21 failed
by Estrella Zaton Martin
Hello,
I'm trying to import the fedora 21 distro from rsync or dvd with:
cobbler import --path=/mnt/iso --name=fedora21 --arch=x86_64
but it fails with !!! TASK FAILED !!!
After, I tried to add the distro uploaded before with:
cobbler distro add --name=fedora21-x86_64
--ksmeta="tree=ftp://nas-deploy.ll.iac.es/media/fedora/releases/21/Fedora/x86_64/os/"
kernel=/var/www/cobbler/ks_mirror/fedora21-x86_64/images/pxeboot/vmlinuz
initrd=/var/www/cobbler/ks_mirror/fedora21-x86_64/images/pxeboot/initrd.img
--arch=x86_64 --breed=redhat --os-version=fedora21
and it seems to be ok, but if I do: cobbler distro list or cobbler
report, no distros appear...
Is there anyone could have imported the fedora21 distro? how?
Thank you and best regards,
Estrella
--
Estrella Zatón Martín
Ingeniero del GSC. Servicios Informáticos Comunes.
Instituto de Astrofísica de Canarias
C/Via Lactea s/n
38200 La Laguna, Tenerife. España
Tfno: +34 922 605 320
Fax: +34 922 605 210
email: ezaton(a)iac.es
http://www.iac.es
---------------------------------------------------------------------------------------------
ADVERTENCIA: Sobre la privacidad y cumplimiento de la Ley de Protección de Datos, acceda a http://www.iac.es/disclaimer.php
WARNING: For more information on privacy and fulfilment of the Law concerning the Protection of Data, consult http://www.iac.es/disclaimer.php?lang=en
9 years, 1 month
Cobbler login
by Scott Mattan
I don't have specifics on why or what was done before this happened... as I
typically use the command line anyway. However it seems that the web
interface for Cobbler has stopped authenticating. It always responds with
invalid password and or username. I have tried re-installing the
interface, recreating the user among other things exhausting my options.
The only error that I can seem to come across is this:
Fri Feb 27 17:56:36 2015 - INFO | Exception occured: <type
'exceptions.AttributeError'>
Fri Feb 27 17:56:36 2015 - INFO | Exception value: BootAPI instance has no
attribute 'authn'
Fri Feb 27 17:56:36 2015 - INFO | Exception Info:
File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 2087, in
_dispatch
return method_handle(*params)
File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 1886, in
login
if self.__validate_user(login_user,login_password):
File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 1783, in
__validate_user
return self.api.authenticate(input_user,input_password)
File "/usr/lib/python2.6/site-packages/cobbler/api.py", line 1025, in
authenticate
rc = self.authn.authenticate(self,user,password)
As it seems to be an issue directly with python code... (although I can't
imagine why it would suddenly change) I am honestly not sure what to do.
Any help is greatly appreciated.
Thanks
Scott
9 years, 1 month
cobbler get-loaders
by Uma Murali
Hi,
I am doing a proof-of-concept using cobbler. I would require help on couple
of things:
- How can I download the stuff that "cobbler get-loaders" helps from an air
gapped environment [not connected to internet]. Is there a FTP link for me
to download and transfer to my cobbler server [that is not connected to
internet]. There is no proxy currently for connection from the cobbler
server
- Is there any API documentation for cobbler that we want to integrate with
the orchestration layers?
Thanks
9 years, 1 month
cobbler LDAP authentication, multiple CNs
by Cory Ringdahl
Hi,
I'm trying to set Cobbler 2.6 up with LDAP authentication against our AD
environment. Using the standard LD config per example works fine, but we
need to allow only certain CNs access to log in.
We were able to get this to work with authn_passthru and Apache with our
existing Cobbler 1.6 (I know, I know), but my tests with this and Cobbler
2.x have failed in the past. I've even tried authn_pam with Winbind, but
this seems to fail in some nebulous space somewhere in Winbind during the
auth process (though various winbind tools do communicate with AD properly).
Note that authz_ownership is not a tenable solution for us, as we have
multiple departments with overlapping responsibilities, and multiple
Cobbler environments with targeted uses (eg customer equipment, internal
prod, internal dev, etc)
Any help would be very much appreciated!
Thanks,
Cory.
9 years, 2 months
Fedora 21 "Everything" import fails
by Gary Algier
Hello,
I have been trying to import Fedora 21 into my Cobbler servers. One is
running 2.6.5, one is running 2.6.6. I did the needed "cobbler signature
update" but my attempts ultimately fail:
root@choo 106% cobbler import
--path=rsync://mirror.uber.com.au/fedora/fedora/linux/releases/21/Everything/x86_64/os
--name=Fedora-21-x86_64 --kickstart="/var/lib/cobbler/kickstarts/default.ks"
task started: 2015-02-18_094431_import
task started (id=Media import, time=Wed Feb 18 09:44:31 2015)
Found a candidate signature: breed=redhat, version=rhel6
Found a candidate signature: breed=redhat, version=rhel7
Found a candidate signature: breed=redhat, version=fedora21
Found a matching signature: breed=redhat, version=fedora21
Adding distros from path /var/www/cobbler/ks_mirror/Fedora-21-x86_64:
No distros imported, bailing out
!!! TASK FAILED !!!
(both versions fail the same)
Am I perhaps trying to get Everything when I should not be? Is there any
better way to get a _complete_ Fedora 21? I see that Fedora 21 has broken
things down into multiple "products". Will I need to instead create 3
different distros in Cobbler (that's a lot of disk space) and then still not
be able to get everything? How do I otherwise have a local copy of a complete
inventory of all the available RPMs? Everything has 50202 RPMs, Server only
has 2494 and it is missing things I want.
I noticed that Fedora 20 documented how to import into Cobbler, but Fedora 21
documentation leaves this out.
--
Gary Algier, WB2FWZ gaa(a)ulticom.com +1 856 787 2758
Ulticom Inc., 1020 Briggs Rd, Mt. Laurel, NJ 08054 Fax:+1 856 866 2033
9 years, 2 months
custom hw_detect script not working due to biosdevname
by Jagga Soorma
Hi All,
We have been using cobbler to provision servers for a few weeks now on
hp hardware without any issues. We just got one dell server and all
of a sudden my networking is screwed up and looks like it is due to
how dell servers behave due to the biosdevname package by default. On
the dell server my interface is setup as em1 instead of eth0 and this
is what I am doing in one of my cobbler snippets that is now broken
due to me looking explicitly for eth0:
--
$ cat centos66/hw-detect
#set $mac = $getVar('$mac_address_eth0')
#if $mac
#set $mac_prefix = $mac[0:8]
#if $mac_prefix == "00:0c:29" or $mac_prefix == "00:05:69" or
$mac_prefix == "00:50:56"
#set global $machinetype='virtual'
#else
#set global $machinetype='physical'
#end if
#end if
--
This is just a quick way for me to detect if it is a virtual or
physical machine. How can I test for the existence of em1 instead?
So basically it would check eth0 if that is what is being defined by
the user or em1 if that is what is being added on the "cobbler system
add" command.
I tried just using $getVar("mac_address") but that does not seem to
work. Any help would be greatly appreciated.
Thanks!
9 years, 2 months
How to make a snippet that configures Dual software raid on /dev/sda /dev/sdb
by Jennifer Patrick
How Would I go about (in a snippet) creating a recipe/snippet that creates
two raid/pv/lv off of two disks? Basically I want it to look like this:
/dev/sda (800gb)
---200GB Raid-1/PV-root/LV-root =/dev/md0
---600GB Raid-1/PV-wite/LV-write =/dev/md1
/dev/sdb (800GB)
---200GB Raid/PV-root/LV-Root/Raid 1 =/dev/mdo
---600GB Raid-1/PV-write/LV-write =/dev/md1
FYi, we're using software raid, but I'm only wanting to utilize the first
two disks for the raid volumes, and have two raid "partitions" created,
along with 2 PV's and 2 LV's, so we have a /dev/md0 bootable drive that's
200GB and a "write" drive that's 600GB and /dev/md1.
I have no problem doing this manually through the installer, just wondering
how to automate it? Whenever I automate it, it allocates all 800GB on each
disk for RAID 1, and just created a /dev/md0.
Here's my current snippet: (which I know is wrong)
# Disk Partitioning
# Use LVM, and wipe out anything that already exists
d-i partman/early_command string vgs --separator=: --noheadings | cut -f1
-d: |
while read vg ; do vgchange -an \$vg ; done ; pvs --separator=:
--noheadings | c
ut -f1 -d: | while read pv ; do pvremove -ff -y \$pv ; done; mdadm --stop
--forc
e /dev/md*; /bin/dd if=/dev/zero of=/dev/sda bs=512 count=1; /bin/dd
if=/dev/zer
o of=/dev/sdb bs=512 count=1; /bin/dd if=/dev/zero of=/dev/sdc bs=512
count=1; /
bin/dd if=/dev/zero of=/dev/sdd bs=512 count=1; /bin/dd if=/dev/zero
of=/dev/sde
bs=512 count=1; /bin/dd if=/dev/zero of=/dev/sdf bs=512 count=1; /bin/dd
if=/de
v/zero of=/dev/sdg bs=512 count=1; /bin/dd if=/dev/zero of=/dev/sdh bs=512
count
=1;
# Disk Partitioning
d-i partman-basicfilesystems/choose_label string gpt
d-i partman-basicfilesystems/default_label string gpt
d-i partman-partitioning/choose_label string gpt
d-i partman-partitioning/default_label string gpt
d-i partman/choose_label string gpt
d-i partman/default_label string gpt
d-i partman-lvm/device_remove_lvm boolean true
d-i partman-md/device_remove_md boolean true
d-i partman-lvm/confirm boolean true
d-i partman-auto/disk string /dev/sda
/dev/sdb
d-i partman-auto/method string raid
d-i partman-auto-lvm/new_vg_name string vg0
d-i partman-auto-lvm/guided_size string 50%
d-i partman-auto/expert_recipe string \
efi-lvm :: \
256 10 256 free \
\$iflabel{ gpt } \
method{ biosgrub } \
\$primary{ } \
\$lvmignore{ } \
format{ } \
.\
50% 30 50% raid \
\$gptonly{ } \
\$lvmignore{ } \
\$primary{ } \
method{ raid } \
.\
140000 50 140000 ext4 \
\$defaultignore{ } \
\$lvmok{ } \
lv_name{ root } \
method{ format } \
format{ } \
use_filesystem{ } \
filesystem{ ext4 } \
mountpoint{ / } \
label{ Root } \
.\
6000 40 6000 swap \
\$defaultignore{ } \
\$lvmok{ } \
lv_name{ swap } \
method{ swap } \
format{ } \
.
d-i partman-auto-raid/recipe string \
1 2 0 lvm - /dev/sda2#/dev/sdb2 \
.
d-i partman-md/confirm boolean true
d-i partman-partitioning/confirm_write_new_label boolean true
d-i partman/choose_partition select Finish
partitioning
and write changes to disk
d-i partman/confirm boolean true
d-i partman-md/confirm_nooverwrite boolean true
d-i partman/confirm_nooverwrite boolean true
d-i mdadm/boot_degraded boolean true
Any help?
This is on Ubuntu Trusty 14.04
--
Jen
9 years, 2 months
