Add descriptions to PXE menu entries?
by petermity
I would like to be able to append some explanatory text to [some
of] the PXE menu entries.
I can see that the Cobbler-generated pxelinux.cfg/default file
has a MENU LABEL line for each entry. I can see in the
pxeprofile.template file that this is from variable $menu_label.
But I don't see any way to modify or append to it from anything
in profile dumpvars. Is there a way? If not, is this a planned
enhancement?
That is, instead of seeing:
Fedora14-i386-Web1
Fedora14-i386-Web2
one might see:
Fedora14-i386-Web1 -- For internal intranet web servers
Fedora14-i386-Web2 -- For web servers on the DMZ
13 years, 1 month
cobbler check - how disable warnings?
by petermity
The "cobbler check" command complains about iptables - but I have
the firewall services turned off. How can I disable the warning, or
otherwise fool Cobbler into not complaining about it?
Likewise, at this time I don't really need to build Debian-based
systems - I'd like to play with it soon, but for the moment I'd
like to stop the complaint about debmirror.
Likewise, the boot-loaders. I don't need anything but x86
support. How can I stop the complaint without doing "cobbler
get-loaders"? (Which I couldn't even do originally because it
still has no proxy support - see year-old issue #572 - I had to
use a different network to be able to do it).
13 years, 1 month
pxelocal.template and $pxe_menu_items
by Pablo Iranzo Gómez
Hi
I would like to achieve something similar to pxedefault.template but with the custom options of pxelocal.template after a system has been provisoned.
The idea is to offer the full range of profiles to each system as an aditional option.
What I did was to put $pxe_menu_items stanza on the pxelocal.template as I did with pxedefault.template, but no matter what I do, it doesn't get rendered.
After looking at the code at pxegen.py, I can see the metadata["pxe_menu_items"] in "make_actual_pxe_menu" (which outputs pxelinux.cfg/default) but not on the function referencing pxelocal.template ("write_pxe_file"), so my guess is that this is not implemented.
¿any hint?
Thanks in advance
Pablo
--
Pablo Iranzo Gómez (Pablo.Iranzo(a)redhat.com)
Senior Global Profesional Services Consultant (RHCA, RHCSS, RHCDS, RHCVA, RHCE, RHCSP) #804006196923216
Phone: +34 645 01 01 49 (CET/CEST)
GnuPG KeyID: 0xFAD3CF0D
13 years, 1 month
Cobbler version variable?
by petermity
I would like to note the version of Cobbler used to create a unit - that
is, in %post, grab the version string and copy it into a file in the
created unit's /root directory, similar to how Cobbler's $kickstart_done
puts the kickstart there as cobbler.ks.
Doing profile dumpvars, I don't see Cobbler's version string. Is there a
way to do this?
13 years, 2 months
Apache httpd warning about FQDN
by petermity
After setting up Cobbler 2.0.10, during system startup, or if I
restart httpd manually, I get:
Starting httpd: httpd: Could not reliably determine the server's
fully qualified domain name, using 127.0.0.1 for ServerName
I fixed it manually by setting /etc/httpd/conf/httpd.conf
ServerName to the IP of eth0, but is this something that
Cobbler's system setup could take care of, or that "cobbler
check" should at least report? (I didn't notice it at first).
This PC is dedicated to Cobbler use and is on no network (just
connected to a switch to build targets).
13 years, 2 months
need to re-run cobbler aclsetup after all cobblerd restarts
by Tom Georgoulias
I built a new cobbler server using cobbler-2.0.10-1.el5.noarch.rpm from
EPEL-Testing and noticed that the ACLs have to be redone every time that
cobblerd is restarted. Can anyone else confirm this? I observed this
behavior on 2.0.9 as well, but not on 1.6.6 (which was the release I was
using previously).
Here's the process I'm using:
As root, grant permissions to my dept group name:
# cobbler aclsetup --addgroup=GROUPNAME
As a user that group:
$ cobbler
usage
=====
cobbler <distro|profile|system|repo|image> ...
[add|edit|copy|getks*|list|remove|rename|report] [options|--help]
cobbler
<aclsetup|buildiso|deploy|import|list|report|reposync|sync|validateks|version>
[options|--help]
As root, restart cobblerd:
# service cobberd restart
After the restart,
$ cobbler
User cannot run command line, need read access to /var/lib/cobbler/web.ss
As root, regrant the permissions:
# cobbler aclsetup --addgroup=GROUPNAME
After this, everything works.
Tom
13 years, 2 months
.link_cache warning on cobbler sync
by petermity
Every time I do "cobbler sync", as part of the output I get
this:
cleaning link caches
running: find /var/lib/tftpboot/.link_cache -maxdepth 1 -type f -links 1
-exec rm -f '{}' ';'
received on stdout:
recieved on stderr: find: `/var/lib/tftpboot/.link_cache': No such file or
directory
running: find /var/www/cobbler/.link_cache -maxdepth 1 -type f -links 1
-exec rm -f '{}' ';'
received on stdout:
recieved on stderr: find: `/var/www/cobbler/.link_cache': No such file or
directory
The sync seems to work and reports no other problems.
What do I need to do to fix this so that there are no warnings or
errors when a sync is done?
13 years, 2 months
MemTest bug still exists - why?
by petermity
When I first tried Cobbler, choosing MemTest in the PXE menu just
flickered and did nothing. I quickly realized it's because its
image is in the wrong place on the server.
Searching the mailing list, this was discussed, and a patch
suggested, over 2 years ago. Over 1 year ago, Trac issue #574
was entered for it.
Is there a reason it hasn't been fixed yet?
For now, I fixed it manually. Actually, fixing it manually, it
gets broken again at the next "cobbler sync". To work around it,
I created file /var/lib/cobbler/triggers/sync/post/fix-memtest
with content:
#!/bin/bash
cp /var/lib/tftpboot/memtest* /var/lib/tftpboot/images
and did chmod +x on it. Now MemTest works after "cobbler sync".
13 years, 2 months
