On Wed, Apr 4, 2012 at 9:20 AM, <[email protected]> wrote:
> Complete trace here.
>
> http://pastebin.com/HbadQx64
Did you install from source or RPM? If from RPM, could you do a "rpm
-V cobbler" and look to see if the templar.py file was modified? If
from source (and even if from RPM), take a look in the
cobbler/templar.py file in the site-packages directory for your python
version. You should see code similar to this in the __init__ function:
def __init__(self,config=None,logger=None):
"""
Constructor
"""
if logger is None:
logger = clogger.Logger()
self.logger = logger
if config is not None:
self.config = config
self.api = config.api
self.settings = config.settings()
The important part is that last line, where it creates self.settings.
The stack dump seems to be saying that doesn't exist in the Templar
instance. If that looks ok, I'm not sure what the issue is. The
manage_in_tftpd.py module creates the Templar class with a valid
config (or it SHOULD be valid), so if there's an error there something
is very messed up internally.
I'm not sure why we allow a Templar instance to be created optionally
without a config, there doesn't seem to be a use for that, so I'm
wondering if it should throw an error in that case.
You could modify the above code in templar.py to add a "else: raise
Exception" to see if it is in fact being created without a proper
config.
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
