Hi!
I'm going nuts.
After upgrading our Spacewalk server to 0.8 (and hence cobbler to 2.0) we
can't get the systems to set their ip-address statically any more.
After checking, testing, editing, testing, checking, testing, editing and
more testing I'm 99% sure that I get the *profile* kickstart file instead of
the *system* kickstart file, but I don't understand why.
The system kickstart file contains the
'post_install_network_config'-snippet, but the profile kickstart doesn't,
and the /root/cobbler.ks left on the system after install doesn't include
the code that should have been expanded from the snippet. AND of course the
system doesn't have the ip-address set to static.
Anybody else with these problems?
Any pointers?
/Jonas
Profile creation done through the web interface selects the option to
have it appear in the PXE menu. The opposite is true for
sub-profiles. Is this a bug? I think that it should be the same for
profiles and sub-profiles....
pxegen.py
367 for profile in profile_list:
368 if not profile.enable_menu:
369 # This profile has been excluded from the menu
370 continue
Thoughts?
Hi
i have just migrated from cobbler 1.6.x to xobbler 2.0.3.
I used to use external authentification with CAS and ldap and i have
made this configuration based on the kerberos page on the wiki
https://fedorahosted.org/cobbler/wiki/CobblerWithKerberos
But as i move to 2.0.x it didn't work anymore.
Then is it possible to make the external authentification work with 2.0.x
Can i still use mod_python handler instead of django?
i have to admit i m a bit puzzled by the update
So basically in a kickstart profile/distro/system record if you set standalone kernel options as
Kernel Options : {'vnc': '', 'vncpassword': 'foo'}
the kickstart will get rendered as
/sbin/grubby --update-kernel=`/sbin/grubby --default-kernel` --args="vnc= vncpassword=foo"
instead of
/sbin/grubby --update-kernel=`/sbin/grubby --default-kernel` --args="vnc vncpassword=foo"
(extra '=' after vnc). The attached patch resolves this issue. Originally this was reported as part of spacewalk https://bugzilla.redhat.com/show_bug.cgi?id=529277 and the investigation led to this cobbler issue and fix.
Partha
Hi
i have just updated my version of cobbler from 1.6.8 to 2.0.3.
I pick the src.rpm and rebuild the two package for my centos 5 server.
and when i want to acces to the /cobbler_web/ url i got the following error
Environment:
Request Method: GET
Request URL: http://cobbler.int-evry.fr/cobbler_web/
Django Version: 1.1.1
Python Version: 2.4.3
Installed Applications:
['django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'cobbler_web']
Installed Middleware:
('django.middleware.common.CommonMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware')
Traceback:
File "/usr/lib/python2.4/site-packages/django/core/handlers/base.py" in
get_response
92. response = callback(request, *callback_args,
**callback_kwargs)
File "/usr/share/cobbler/web/cobbler_web/views.py" in index
64. html = t.render(Context({
Exception Type: AttributeError at /cobbler_web/
Exception Value: 'NoneType' object has no attribute 'version'
Does someone know how to solve that problem?
Thanks in advance
Hello,
I've been using the Cobbler 2.x from the testing area and overall it seems fairly stable. When will that version be moved to the standard EPEL repository?
Mike
According to the wiki page at
https://fedorahosted.org/cobbler/wiki/AuthorizationWithOwnership ,
anyone who is in users.conf can create new cobbler objects. I've had
opposite luck in my 1.6.6 production installation.
I'm working with a testuser listed in [testgroup] in users.conf. The
user can create profiles only when moved to [admin]. Same problem
through the web interface or the XMLRPC API. Here's my cobblerd.log
output:
2010-03-05 14:57:37,603 - api - login attempt; user(testuser)2010-03-05
14:57:37,603 - api - authenticate; ['testuser', True]
2010-03-05 14:57:37,604 - api - login succeeded; user(testuser)
2010-03-05 14:57:47,263 - api - new_repo; user(testuser)2010-03-05
14:57:47,263 - api - calling authorize for resource ['new_repo', None,
None]; user(testuser)
2010-03-05 14:57:47,264 - api - authorization result: True; user(?)
2010-03-05 14:58:06,184 - api - calling authorize for resource
['modify_repo', <cobbler.item_repo.Repo instance at 0x1d35758>, 'name';
user(testuser)r):56,692 - api - get_profiles; user(?)
2010-03-05 14:58:06,184 - api - Exception occured:
cobbler.cexceptions.CX2010-03-05 14:58:06,184 - api - Exception value:
'user does not have access to resource: modify_repo'
2010-03-05 14:58:06,185 - api - Exception Info:
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 1567,
in _dispatch
return method_handle(*params) File
"/usr/lib/python2.4/site-packages/cobbler/remote.py", line 1409, in
modify_repo
self.check_access(token, "modify_repo", obj, attribute)
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 1013,
in check_access rc = self.__authorize(token,resource,arg1,arg2)
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 1044,
in __authorize raise CX(_("user does not have access to resource:
%s") % resource)
Any ideas?
-CG
Hi,
I could successfully install a kvm guest on RHEL 5.4 via koan.
Now I read that using the virt-io-drivers can increase disk and network performance
of the guest. There is a parameter called "--os-variant=virtio26" for virt-install
so that these drivers are automatically being used. Is it possible to tell
koan to use this parameters as well ?
Kind Regards
Tim
Hello All,
Could someone give me an example of how one would import VMware ESX4 into
cobbler? A regular import copies the files from the mounted iso image, but
does not create distro / profile information. Perhaps I missed a step.
There really is not much information on the web. Just a brief step by step
is fine. (and perhaps the rough syntax?)
I would really be grateful for the information.
Hej.
My old trigger don't work any more. None of my test triggers are
executed either.
I have them in
/var/lib/cobbler/triggers/install/post
How are you supposed to write triggers these days?
I am using s shorter variant of the cfenginge ppkeys trigger found on.
https://fedorahosted.org/cobbler/wiki/CobblerTriggers
I have the cfengine on the same server as cobbler. But it dont work any
more.
I have also tried to copy and edit a trigger in the.
site-packages/cobbler/modules
i used the install_post_log.py as template
But id don't seam to run either.
Any one could tell me how to do it the right way?
cheers
--
-------------------------------------------
Systemexpert jonas.hagberg(a)it.uu.se
Jonas Hagberg tel 018 - 471 1026
UPPMAX fax: 018 - 51 19 25
Uppsala universitet
Box 337, Lägerhyddsv 2E, Hus 4, room 4111
751 05 Uppsala www.uppmax.uu.se
-------------------------------------------