On 09/29/2009 01:34 PM, Bryan Schneiders wrote:
cobbler-2.0.0-1.fc10.noarch
cobbler-web-2.0.0-1.fc10.noarch
I'm seeing this error on various web ui links. Refreshing the page usually makes it
go away. Clicking the same link immediately after a correct page finishes loading is an
easy way to reproduce the error.
MOD_PYTHON ERROR
ProcessId: 22784
Interpreter: 'fs1.woti.com'
ServerName: 'fs1.woti.com'
DocumentRoot: '/var/www/html'
URI: '/cobbler_web/ksfile/list'
Location: '/cobbler_web'
Directory: None
Filename: '/var/www/cobbler_web'
PathInfo: '/ksfile/list'
Phase: 'PythonAuthenHandler'
Handler: 'cobbler_web.views'
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1537,
in HandlerDispatch
default=default_handler, arg=req, silent=hlist.silent)
File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1202,
in _process_target
module = import_module(module_name, path=path)
File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 304, in
import_module
return __import__(module_name, {}, {}, ['*'])
File "/usr/share/cobbler/web/cobbler_web/views.py", line 16,
in<module>
import cobbler.item_distro as item_distro
File "/usr/lib/python2.5/site-packages/cobbler/item_distro.py", line 108,
in<module>
[ "os_version","generic26",0,"OS
Version",True,"Needed for some virtualization
optimizations",codes.get_all_os_versions()],
File "/usr/lib/python2.5/site-packages/cobbler/codes.py", line 67, in
get_all_os_versions
results = utils.uniquify(results)
AttributeError: 'module' object has no attribute 'uniquify'
This one we know about as it has been reported a few times. The going
theory is that it on (except on Fedora, where it works for me) a path
collision with another possibly installed utils.py, or something with
the module load order from mod_python.
It is on my list to debug this week. Even if it remains a mystery, a
workaround is easily done. I just need to install a VM and test this.
For tracking purposes:
https://fedorahosted.org/cobbler/ticket/504
We'll get it resolved for 2.0.1.
Thanks!
--Michael