Michael DeHaan wrote:
There are instructions for installing a cobbler server on RHEL-5 on
et.redhat.com. On little catch though -- apparently cobbler's
mod_python file tracking solution (which is very happy on Fedora),
still doesn't work on RHEL5 at this point according to at least one
report. (I thought it just needed python2.4, but maybe Apache is the
cause instead?). The result of this is that you may see an error in
Anaconda during install, that includes a python 2.4 traceback from
the host. The tracking code is due for an overhaul, so a quick
workaround is as follows ...
diff --git a/cobbler/action_sync.py b/cobbler/action_sync.py
index 55c558f..d0efa06 100644
--- a/cobbler/action_sync.py
+++ b/cobbler/action_sync.py
@@ -213,7 +213,7 @@ class BootSync:
mod_python_ok = True
- for x in [ "redhat-release-4", "redhat-release-3",
"centos-release-4", "centos-release-3" ]:
+ for x in [ "redhat-release-5", "redhat-release-4",
"redhat-release-3", "centos-release-4", "centos-release-3" ]:
if release_info.lower().find(x) != -1:
mod_python_ok = False
Just delete your /etc/httpd/conf.d/cobbler.conf and re-run "cobbler
sync" -- cobbler will regenerate a version of the configuration file
that doesn't have the status tracking part enabled. Syslog-based
tracking
will still work, as will "cobbler status" (just with less data).
I'll work on getting a better kickstart tracking solution in for
future releases.
--Michael
False alarm. Apparently this might have been a permissions issue.
You shouldn't see this if you install from the RPM. RPMs are good :)
I'm still looking at improving tracking for things like RHEL4, however.
--Michael
