yum upgrade to 1.2.6-1.el5
by Harry Hoffman
Just upgraded to the latest cobbler from epel-testing... the
post-install script fails :-(
Updating : cobbler ####################### [ 5/10]
profile CentOS-5.2-x86_64 not found, inheritance not possible
Stopping cobbler daemon: [ OK ]
Starting cobbler daemon: Traceback (most recent call last):
File "/usr/bin/cobblerd", line 32, in ?
api = bootapi.BootAPI()
File "/usr/lib/python2.4/site-packages/cobbler/api.py", line 90, in
__init__
self.deserialize()
File "/usr/lib/python2.4/site-packages/cobbler/api.py", line 448, in
deserialize
return self._config.deserialize()
File "/usr/lib/python2.4/site-packages/cobbler/config.py", line 186,
in deserialize
serializer.deserialize(self._profiles)
File "/usr/lib/python2.4/site-packages/cobbler/serializer.py", line
125, in deserialize
rc = storage_module.deserialize(obj,topological)
File
"/usr/lib/python2.4/site-packages/cobbler/modules/serializer_yaml.py",
line 136, in deserialize
obj.from_datastruct(datastruct)
File "/usr/lib/python2.4/site-packages/cobbler/collection.py", line
144, in from_datastruct
item = self.factory_produce(self.config,seed_data)
File
"/usr/lib/python2.4/site-packages/cobbler/collection_profiles.py", line
41, in factory_produce
return profile.Profile(config).from_datastruct(seed_data)
File "/usr/lib/python2.4/site-packages/cobbler/item_profile.py", line
87, in from_datastruct
self.set_parent(self.parent)
File "/usr/lib/python2.4/site-packages/cobbler/item_profile.py", line
131, in set_parent
raise CX(_("profile %s not found, inheritance not possible") %
parent_name)
cobbler.cexceptions.CX: 'profile CentOS-5.2-x86_64 not found,
inheritance not possible'
[FAILED]
error: %post(cobbler-1.2.6-1.el5.noarch) scriptlet failed, exit status 1
Any ideas?
Cheers,
Harry
14 years, 7 months
network ordering
by Christopher Johnston
So I have some servers with a few network cards installed and because the
kernel does a poor job of ordering them correctly during an install they
come up out of order (pci=bfsort does not help). I havnt looked to deep
into the snippet just yet, but on a specific system where I have the
following:
eth0 : unconfigured
eth1 : unconfigured
eth2 : non-routeable network (heartbeat)
eth3 : configure routeable network
My BIOS is configured to PXE boot on eth3. So in cobbler I have it setup
like so with eth0 empty, eth2 configured our private 192.168 interface and
eth3 configured with the routable interface.
interface : eth0
mac address :
bonding :
bonding_master :
bonding_opts :
is static? : False
ip address :
subnet :
static routes : []
dns name :
dhcp tag :
virt bridge :
interface : eth2
mac address : 00:1F:29:E1:54:AE
bonding :
bonding_master :
bonding_opts :
is static? : True
ip address : 192.168.x.x
subnet : 255.255.255.0
static routes : []
dns name : edge01.core.lon04.mtt
dhcp tag :
virt bridge :
interface : eth3
mac address : 00:1F:29:E1:54:AC
bonding :
bonding_master :
bonding_opts :
is static? : True
ip address : 10.x.x.x
subnet : 255.255.255.0
static routes : []
dns name : edge01.lon04.mtt
dhcp tag :
virt bridge :
When I look at the kickstart file, it looks to be ordering them with a
different configuration then I wanted using the "old" style config? how do
I get it to use the "new" style config?
# Network information
# Using "old" style networking config. Make sure all MAC-addresses are in
cobbler to use the new-style config
network --bootproto=static --ip=10.123.200.36 --netmask=255.255.255.0
--gateway=10.123.200.1 --hostname=edge01.lon04.mtt --device=eth0 --onboot=on
network --bootproto=static --ip=192.168.123.36 --netmask=255.255.255.0
--gateway=10.123.200.1 --hostname=edge01.lon04.mtt --device=eth1 --onboot=on
network --bootproto=dhcp --device=eth2 --onboot=on
A few questions:
1) eth0 should not even be used, let alone why is it a requirement to have
eth2 in my cobbler system record? I have alot of hosts where eth0 is
available but not even plumbed up.
2) eth2/eth3 are the NICs I want to use, but why did they end up going to
eth0/eth1?
3) where did the eth2 interface come into the picture here using dhcp?
15 years, 1 month
PXE boot sub menu's
by Glenn Bailey
Now I'm not sure if this is even possible, but I thought I'd throw it out there. Basically, having submenus within the PXE boot menu. An example would be the following:
CentOS
- CentOS 4
- i386
- Web build
- App build
- Dev build
- x86_64
- CentOS 5
- i386
- x86_64
- etc
My build process does not include MAC addresses, so we basically have to select the OS then I'll
have some post scripts to pull the chassis serial # for configuration info from a config database.
Just wanted something a bit cleaner that the default method, but of course this is just me being
anal ;-)
--
glenn
terremark worldwide
15 years, 1 month
[CONFIRMED] the webapp and the zero length file problem is a YAML bug... solution / testing welcome
by Michael DeHaan
Cobbler 1.4.3, currently in git, eliminates the infinite recursion
traceback that causes the zero length file writes in Cobbler.
It does this by replacing the YAML library with a better implementation.
I'm currently waiting on a dependency of PyYAML to get package reviewed
(so that we can also build PyYAML 1.4.3 in EPEL), and as soon as that is
done, we will release Cobbler 1.4.3 with the fix.
Enterprising users who would like to help me test can install PyYAML
from Fedora or EPEL5 and use the latest 1.4.3 git. Just do "make
webtest" to install the latest code and restart cobblerd, then log into
the web app and it should not have the same problem. If it does have
problems, the problem is more fundamental, though the traceback points
to YAML and nothing else.
You may also wish to install libyaml in your testing as that makes
cobbler as fast as it was before for reading/writing, without it it is a
little slower. We will include libyaml in cobbler's RPM requirements
once available in Fedora/EPEL.
Thanks for the help and thanks again for the patience on this one.
--Michael
15 years, 1 month
Re: Open Roadmap Discussion for 1.5/1.6
by JAmes Atwill
----- "Michael DeHaan" <mdehaan(a)redhat.com> wrote:
> (Side question: who's workflow for setting up machines involves
> setting the asset tags? And if so, what do you set them to?)
I can only speak for Dell machines, but the Asset Tag (aka Service Tag)
seems to be like the human-friendly serial #. It's picked by Dell
and assigned by them. There's a sticker on the front of all our P2950s
with a matching value.
[root@example ~]# dmidecode | grep "Serial Number"
YMMV.
JAmes
--
James Atwill - Systems Architect
Digital Ocean Marketing
www.digitaloceanmarketing.com
15 years, 1 month
anamon misses modules on RHEL4 installation
by Vreman, Peter
To get anamon working on a RHEL4.6 installation I have to wget also the following files:
operator.so { this .so is python version dependent }
shlex.py
xmllib.py
xmlrpclib.py
How to solve this? Shall I also make the files available through http?
On which distro's is the anamon code developped?
Regards,
Peter
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
15 years, 1 month
Re: RHN registration snippet
by James Cammarata
On Fri, 27 Feb 2009 21:00:23 +0000 (GMT), Rob Lazzurs <lazzurs(a)lazzurs.net>
wrote:
> On Fri, 27 Feb 2009, James Cammarata wrote:
>
>> I noticed the redhat_register snippet accesses a couple of variables
>> (also
>> shown in dumpvars), however the only one it seems you can edit is the
key
>> variable. Are the edit commands missing some options, or can someone
>> point me to some documentation on how to actually use this?
>>
>> # cobbler system dumpvars --name ks-test | grep redhat
>> 'breed': 'redhat',
>> 'redhat_management_key': '',
>> 'redhat_management_server': 'xmlrpc.rhn.redhat.com',
>> 'redhat_management_type': 'off',
>>
>> Hopefully it's not expected of people to hand-edit the config files to
>> use
>> this :)
>
> Hello James,
>
> If you wish to edit the management server then yes you will have to edit
> the configuration file in /etc/cobbler/settings. This file will also
have
> some other settings you have to change, the file is well documented and
> running 'cobbler check' on the command line should help you with any
> further settings you need to change.
>
> Take care.
>
> --
> Rob Lazzurs
Thanks guys, I didn't think to look in settings...
Might be a corner case, but if anyone had two different RHN servers they
might register to (I've actually seen this, last company had a completely
different satellite server for their lab/testing that was isolated from
production), this would be a limitation.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
15 years, 1 month
