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
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
Interest in moving from mod_python to mod_wsgi?
by Devan Goodwin
The Spacewalk team has been working on moving their stuff to mod_wsgi
and in the process realized that Cobbler still uses mod_python, so
they were wondering if we have any plans to do the same. Looking
around a bit it seems like this is generally regarded as a good idea,
mod_python appears to be considered quite poor for performance and
memory, and I'm hearing it's now unmaintained as well. Looking through
the cobbler source it seems we've got a number of mod_python hacks as
well. mod_wsgi is in Fedora and EPEL as far back as EL4.
Anyone feel this is a particularly bad idea?
Thanks,
Devan
--
Devan Goodwin <dgoodwin(a)rm-rf.ca>
http://rm-rf.ca
14 years
cobbler cli user doesn't work after 1.x to 2.0.1 upgrade
by Chris Kelly
Hello-
I upgraded from 1.x to 2.0.1 and the cobbler cli user no longer works.
example:
[root@admin1 ~]# cobbler system add --name=foobar
cobbler.cexceptions.CX:'user <DIRECT> does not have access to
resource: xedit_system'
[root@admin1 ~]#
Looking around in the source code, I see:
/usr/lib/python2.4/site-packages/cobbler/modules/authz_ownership.py
def authorize(api_handle,user,resource,arg1=None,arg2=None):
"""
Validate a user against a resource.
All users in the file are permitted by this module.
"""
if user == "<DIRECT>":
# CLI should always be permitted
return True
...
so that should fall through fine. However, we are using LDAP
([authentication] module = authn_ldap) and I don't see any such code
in the LDAP module. It doesn't seem that adding similar code to the
authn_ldap.py file (and clearing pyo and pyc files and restarting
cobblerd) does the trick.
We are using the config file to manage users ([authorization] module =
authz_configfile) and adding <DIRECT> as a user there doesn't let root
on the command line back in.
Any ideas? Thanks!
-Chris
14 years
enable batch delete
by Jonathan Sabo
List,
I want to enable the ability to batch delete objects. It was already
present in the view but commented out as possibly too dangerous. I
would like this functionality and the fact that its in the batch
actions section in the webui makes it a bit more difficult to mess up.
It also confirms prior to doing anything just like the other batch
actions.
http://github.com/jsabo/cobbler/tree/batch_delete
Thanks,
Jonathan
14 years, 1 month
few doubts
by Zubin Mithra
Hello,
I just went through the cobbler code base and found a few points worth
querying.
1. Why is it that the default spacing used is that of 3 spaces when 4 spaces
could have been used to achieve pep compliance too?
2. None of the "except" blocks in the code base have a type; this is not a
good practice. I feel this should be put up as a ticket.
for eg:-
try:
import <something>
except ImportError:
<do something>
Zubin Mithra
http://zubin71.wordpress.com
14 years, 1 month
ticket #470 improvised
by Zubin Mithra
Hello,
Attached is the modified patch for ticket #470.
Description:
python-ethtool is imported. If not found rhpl.ethtool is used. Again, If not
found error message notifying that neither of the packages are installed, is
displayed.
Please review and update.
Zubin Mithra
http://zubin71.wordpress.com
14 years, 1 month
Re: ticket #470
by Scott Henson
Excerpts from Zubin Mithra's message of Tue Mar 30 14:36:06 -0400 2010:
> On Wed, Mar 31, 2010 at 12:00 AM, Scott Henson <shenson(a)redhat.com> wrote:
>
> > Excerpts from Zubin Mithra's message of Fri Feb 26 03:06:11 -0500 2010:
> > > https://fedorahosted.org/cobbler/ticket/470
> > >
> > > Attached is the patch for the ticket. Kindly review and patch.
> >
> > Where does one get python-ethtool for el4 and el5? I can't find it in
> > rhn or epel.
>
> Python modules can always be installed from source in a very easy manner.
We try to keep cobbler fully usable on the various flavors of el,
particularly Red Hat and CentOS
> > we probably want to try to use python-ethtool and if we
> > can't, fall back to rhpl. If neither can be found, then throw an
> > exception saying to install one of them.
> >
>
> This can be done. I`ll take care of it in a few days time. Or is there an
> urgency?
No urgency. I think we are good for the moment staying on rhpl.
--
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME
14 years, 1 month
Fwd: Patch for dealing with standalone kernel options
by Partha Aji
Forwarded the patch to wrong mailing list previously..
----- Forwarded Message -----
From: "Partha Aji" <paji(a)redhat.com>
To: cobbler(a)lists.fedorahosted.org
Sent: Monday, March 22, 2010 6:43:35 PM GMT -05:00 US/Canada Eastern
Subject: Patch for dealing with standalone kernel options
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
14 years, 1 month