Commit 335f140534de31335727ceb9ed18ad8b405bf638 fixes the
error 31 -- the rhn_entitlements.can_entitle_server returned 1
in psql but via rhnSQL it was returning None.
Currently rhnreg_ks fails with
Error code: 1While running 'queue.get': caught
exceptions.TypeError : unsupported operand type(s) for -: 'float' and 'str'
which can also be triggered by rhn_check after registration.
It comes from
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/spacewalk/server/apacheRequest.py",
line 119, in call_function
response = apply(func, params)
File "/usr/share/rhn/server/handlers/xmlrpc/queue.py", line 270, in get
self.__update_status(status)
File "/usr/share/rhn/server/handlers/xmlrpc/queue.py", line 136, in
__update_status
if abs(last_boot-self.server.server["last_boot"]) > 60*5:
TypeError: unsupported operand type(s) for -: 'float' and 'str'
and from the fact that that self.server.server["last_boot"] is
a string '0'. The object self.server.server gets populated via
backend/server/rhnHandler.py's
server = rhnServer.get(system_id, load_user = self.load_user)
which then seems to populate the data from rhnServer, and it puts
string '0' into the object instead of 0, even if the type of the
last_boot column is number.
I wonder if something in that row populating code needs to be fixed
to better understand PostgreSQL types ...
--
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
