[PATCH] logging of triggers
by Vreman, Peter
Currently there is no logging that triggers are being run. This patch adds logging for the triggers.
Patch is available at: http://github.com/pvreman/cobbler/commit/5c324a356fe3c0ee9fbceb0801799041...
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.
13 years, 11 months
[PATCH] cobbler-ext-nodes http_port support
by Vreman, Peter
Cobbler-ext-nodes scripts needs also to use http_port to support cobbler running on a different port than 80.
Patch available at: http://github.com/pvreman/cobbler/commit/29d03fb3009b1267e86d6f56e8290883...
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.
13 years, 11 months
Cobbler Web Auth Problems in Master
by Devan Goodwin
I'm seeing some authentication problems with Cobbler web on two
separate machines now, the problem crops up in
8373491156c673a31225daf8503c1f090d20a65b which was a fix for
https://fedorahosted.org/cobbler/ticket/549.
Upon entering login credentials I get:
Environment:
Request Method: GET
Request URL: http://cobblerdev/cobbler_web/settings
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 settings
748. check_auth(request)
File "/usr/share/cobbler/web/cobbler_web/views.py" in check_auth
76. token = remote.login(username, password)
File "/usr/lib/python2.4/xmlrpclib.py" in __call__
1096. return self.__send(self.__name, args)
File "/usr/lib/python2.4/xmlrpclib.py" in __request
1383. verbose=self.__verbose
File "/usr/lib/python2.4/xmlrpclib.py" in request
1147. return self._parse_response(h.getfile(), sock)
File "/usr/lib/python2.4/xmlrpclib.py" in _parse_response
1286. return u.close()
File "/usr/lib/python2.4/xmlrpclib.py" in close
744. raise Fault(**self._stack[0])
Exception Type: Fault at /cobbler_web/settings
Exception Value: <Fault 1: "cobbler.cexceptions.CX:'login failed (testing)'">
In case it's useful my request variable inside views.py.check_auth is:
request
<ModPythonRequest path:/cobbler_web/settings, GET:<QueryDict: {}>,
POST:<QueryDict: {}>, COOKIES:{}, META:{'AUTH_TYPE': 'Basic',
'CONTENT_LENGTH': 0, 'CONTENT_TYPE': None, 'GATEWAY_INTERFACE':
'CGI/1.1', 'HTTP_ACCEPT':
'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8',
'HTTP_ACCEPT_CHARSET': 'ISO-8859-1,utf-8;q=0.7,*;q=0.7',
'HTTP_ACCEPT_ENCODING': 'gzip,deflate', 'HTTP_ACCEPT_LANGUAGE':
'en-us,en;q=0.5', 'HTTP_AUTHORIZATION': 'Basic dGVzdGluZzp0ZXN0aW5n',
'HTTP_CACHE_CONTROL': 'max-age=0', 'HTTP_CONNECTION': 'keep-alive',
'HTTP_HOST': 'cobblerdev', 'HTTP_KEEP_ALIVE': '300', 'HTTP_REFERER':
'http://cobblerdev/cobbler_web/', 'HTTP_USER_AGENT': 'Mozilla/5.0
(X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330
Fedora/3.5.9-1.fc12 Firefox/3.5.9', 'PATH_INFO':
u'/cobbler_web/settings', 'PATH_TRANSLATED': None, 'QUERY_STRING':
None, 'REMOTE_ADDR': '192.168.1.1', 'REMOTE_HOST': None,
'REMOTE_IDENT': None, 'REMOTE_USER': 'testing', 'REQUEST_METHOD':
'GET', 'SCRIPT_NAME': '', 'SERVER_NAME': 'cobblerdev.local.rm-rf.ca',
'SERVER_PORT': 80, 'SERVER_PROTOCOL': 'HTTP/1.1', 'SERVER_SOFTWARE':
'mod_python'}>
I'm using authn_testing but I believe I've seen it with
authn_configfile as well. I've got this cropping up on two Cobbler
installs currently, one was fresh so I don't think I've got anything
misconfigured. I can checkout the revision prior to this one and 'make
webtest' and authentication will then work.
Going to continue digging to see if I can figure out what's up but
wanted to see if anyone's fixed this or knows what might be going on.
Thanks,
Devan
--
Devan Goodwin <dgoodwin(a)rm-rf.ca>
http://rm-rf.ca
13 years, 11 months
[PATCH] Don't mess up ctime during cobbler reposync
by Robert Vogelgesang
Hello,
cobbler trac issue #579 is now resolved, but as I've noted there,
cobbler does mess up the ctime timestamps of a mirrored repo during
the reposync action, which could mislead "createrepo --update --C".
To get this resolved, too, I've created the attached patch. The
patch limits the ctime changing actions to the bare minimum.
This was confirmed by the logging I've added for debugging #579.
But there is a futher bug, and as I'm by no means a real python
programmer, I'm currently unable to tell if there's something
wrong with my patch, or if it's a bug in the logging support.
The problem: The commands are executed as written, but only the parts
of the commands after the pipe symbol are logged; i. e. for cmd1 only
"xargs -0 chown root:apache" is logged, and for cmd2 only
"xargs -0 chmod a+rX". I've done a cursory search in the standard
Python docs for any special meaning of the pipe symbol, but found
nothing.
So I'm asking here for help, to resolve this strange logging problem.
Maybe this is an issue with cobbler's use of python's logging?
Robert
PS.: The patch changes next to nothing with regard to what other
packages are required for cobbler; the findutils package is
required by the initscripts and man packages, and restorecon
comes with policycoreutils which are required for SELinux.
13 years, 12 months
Ping regarding patches
by Ian Ward Comfort
I just wanted to check up on some patches I sent to this list in the
last few weeks, with these message-ids:
<1268952125-25611-1-git-send-email-icomfort(a)stanford.edu>
<1268976365-2149-1-git-send-email-icomfort(a)stanford.edu>
<1268984579-5713-1-git-send-email-icomfort(a)stanford.edu>
<1268986373-6679-1-git-send-email-icomfort(a)stanford.edu>
<1269373736-19738-1-git-send-email-icomfort(a)stanford.edu>
Do the maintainers have any interest in these patches? I'd especially
like to see numbers 2, 4 and 5 upstream, since they're fixes for
fairly serious bugs. If I can help by providing further context or
rationale for any of these, let me know.
--
Ian Ward Comfort <icomfort(a)stanford.edu>
Systems Team Lead, Academic Computing Services, Stanford University
14 years
ISOlinux menu templating patches
by Stuart Sears
Hi all,
Patch attached for comment/criticism. It's my first, be nice :)
The patch adds a 'menutemplate' parameter to the ISO generation methods in
cobbler/action_buildiso
cobbler/api.py
cobbler/remote.py
...and defaults to the included 'HEADER' variable if a template file is
not specified.
I've been using /etc/cobbler/isolinux.cfg.template for this.
Regards,
Stuart
--
Stuart Sears RHCA etc.
"It's today!" said Piglet.
"My favourite day," said Pooh.
14 years
Unexpanded $SNIPPET()
by Wes Hardin
I'm having an issue with one particular $SNIPPET() not being expanded in one
particular kickstart file with Cobbler 2.0.3.1 on CentOS 5.4.
[root@dallcobbler2 repo_mirror]# cat /etc/redhat-release
CentOS release 5.4 (Final)
[root@dallcobbler2 repo_mirror]# rpm -qa cobbler\*
cobbler-web-2.0.3.1-1.el5
cobbler-2.0.3.1-1.el5
I have a kickstart file for EL4 and EL5. The snippet expands and works
correctly in the EL5 kickstart, but when I 'view kickstart' from the system menu
for an EL4 system, I get a literal $SNIPPET() in my kickstart.
I looked back at old list posts and saw a post about changes to the Cheetah
behavior concerning snippets, and while I admittedly didn't understand it fully,
it doesn't really seem to apply here since it is able to be expanded in one
kickstart but not another.
There's really very little difference between my EL4 and EL5 kickstarts, mostly
just the %packages and %post. Originally the EL5 didn't have this snippet in it
(the snippet installs yum on RHEL4), so I copied the line from the EL4 and
pasted exactly as-is into the EL5 kickstart.
Any ideas on what's going on here?
--
/* Wes Hardin */
UNIX System Administrator, IT Engineering Support
Maxim Integrated Products: Innovation Delivered
14 years
Build Tool Changes
by Devan Goodwin
Just pushed some small changes to switch to using Tito to git tag our
releases and do tgz + rpm builds.
http://github.com/dgoodwin/tito
For anyone doing development, this just means you can run devel code
off the latest git head, but install it via rpm if you'd prefer.
'tito build --rpm' will build the latest tagged release for your arch.
'tito build --rpm --test' will build test rpms off the latest git
HEAD, great for devels who want to deploy via rpms.
Once we go to do a new release:
'tito tag' will bump the version, auto-gen the spec file changelog
from commit messages and give you a chance to edit it, then commit and
git tag.
'tito build --srpm' will build a source rpm
With some config changes we can get it set up to tito build --release
will build the source rpm, commit changes to Fedora CVS and submit all
the desired Koji builds. Let me know when, and I can help get this set
up.
I had to tag a new version to get this operational, you'll see a
cobbler-2.0.3.2-1 tag out there, I don't intend for this to be a
public release. (although it can be if we'd like to do one now) Will
try to do some more work to cleanup build process in the coming weeks.
Let me know if you hit any issues.
Cheers,
Devan
--
Devan Goodwin <dgoodwin(a)rm-rf.ca>
http://rm-rf.ca
14 years
UEFI Support?
by Bill Peck
Has anyone started working on UEFI support in cobbler? I'm guessing we
would want to write UEFI configs for x86, x86_64 and ia64. They would
co-exist with pxe and efi entries.
Thoughts?
14 years
Add ability to import VMware ESX with cobbler import
by Jonathan Sabo
Hi,
I wanted to add the ability to import VMware ESX 4 update 1 with
cobbler import. I don't think it affects any other importing of non
vmware esx stuff. Would someone like to test it out other than
myself? I've been able to import VMware ESX media and kickstart ESX 4
update 1 to automatically build ESX hosts.
http://github.com/jsabo/cobbler/tree/esx
[root@localhost ~]# cobbler distro report --name=vmware-esx4u1-x86_64
Name : vmware-esx4u1-x86_64
Architecture : x86_64
Breed : vmware
Comment : esx4.1
Initrd :
/var/www/cobbler/ks_mirror/vmware-esx4u1/isolinux/initrd.img
Kernel :
/var/www/cobbler/ks_mirror/vmware-esx4u1/isolinux/vmlinuz
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart Metadata : {'tree':
'http://@@http_server@@/cblr/links/vmware-esx4u1-x86_64'}
Management Classes : []
OS Version : esx4
Owners : ['admin']
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Template Files : {}
[root@localhost ~]# cobbler profile report --name=vmware-esx4u1-x86_64
Name : vmware-esx4u1-x86_64
Comment :
DHCP Tag : default
Distribution : vmware-esx4u1-x86_64
Enable PXE Menu? : 1
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart : /var/lib/cobbler/kickstarts/sample-esx.ks
Kickstart Metadata : {}
Management Classes : []
Name Servers : []
Name Servers Search Path : []
Owners : ['admin']
Parent Profile :
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Repos : []
Server Override : <<inherit>>
Template Files : {}
Virt Auto Boot : 0
Virt Bridge : xenbr0
Virt CPUs : 1
Virt File Size(GB) : 5
Virt Path :
Virt RAM (MB) : 512
Virt Type : vmware
Thanks,
Jonathan
14 years
