> Judging from the OS release bits below, might you have something /else/? 
> If you're running Cobbler on another platform then perhaps the 
> os_version routine does not work there.
> 
> I'd need more details to speculate further.

I have had a closer look at the code. Here's what I get when I rpm query 
"redhat-release":

$ rpm -q --whatprovides redhat-release
redhat-release-5Server-5.2.0.4

The code is getting the string "5Server" as the version number, then it 
tries to type-cast it as a float which, of course, throws an exception.

Looking on RHN, it seems that the redhat-release package for RHEL5 has 
always provided it in this format:

----------
[...]
Provides

config(redhat-release) = 5Server-5.0.0.9
redhat-release = 5Server-5.0.0.9
[...]
----------
[...]
Provides

config(redhat-release) = 5Server-5.1.0.2
redhat-release = 5Server-5.1.0.2
[...]
----------
[...]
Provides

config(redhat-release) = 5Server-5.2.0.4
redhat-release = 5Server-5.2.0.4
[...]
----------

Note that the desktop version of RHEL5 uses the string '5Client':

$ rpm -q --whatprovides redhat-release
redhat-release-5Client-5.2.0.4

The odd thing is that I have an older version of Cobbler installed on 
another RHEL5 server. The code for os_release() is pretty much identical 
but I have no problems running "cobbler check" there.

Ah...I see the problem. In utils.py, tftpboot_location() is trying to 
determine the location of /tftpboot but I have not yet installed that 
package. So, it calls os_release() to try and guess the default location 
based on the operating system. It works on the other system because 
os_release() is never called, tftpd is installed!

Okay, I will concede that I would not have encountered this and the init 
script problem had I installed the RPM... ;-) But I think these are bugs 
considering that exceptions are being raised for things that Cobbler is 
supposed to be checking. Not critical, I will simply install the tftpd 
package.

Done. That was fixed but now I am getting another exception, this time 
because it does not handle the missing httpd init script (same as the 
missing cobblerd init script). *sigh* I need to think about whether it 
is worth the trouble installing Cobbler manually in an alternate 
location. :-S


Chris

_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler

Reply via email to