Description of problem:
On Satellite 540 registered x86_64 RHEL5 guest (without a host) the provisioning fails on client side during rhn_check (initiating the ks process passes actually) with an error on /var/log/up2date:
---
[Tue Oct 12 10:57:54 2010] up2date updateLoginInfo() login info
[Tue Oct 12 10:57:54 2010] up2date D: login(forceUpdate=True) invoked
[Tue Oct 12 10:57:54 2010] up2date logging into up2date server
[Tue Oct 12 10:57:54 2010] up2date D: rpcServer: Calling XMLRPC up2date.login
[Tue Oct 12 10:57:54 2010] up2date D: writeCachedLogin() invoked
[Tue Oct 12 10:57:54 2010] up2date D: Wrote pickled loginInfo at  1286873874.47  with expiration of  1286877474.47  seconds.
[Tue Oct 12 10:57:54 2010] up2date successfully retrieved authentication token from up2date server
[Tue Oct 12 10:57:54 2010] up2date D: logininfo: {'X-RHN-Server-Id': 1000010022, 'X-RHN-Auth-Server-Time': '1286873877.52', 'X-RHN-Auth': 'kVfxpK2hggoLnaBVFT+Xyg==', 'X-RHN-Auth-Channels': [['rhel-x86_64-server-5', '20101009075236', '1', '1'], ['rhn-tools-rhel-x86_64-server-5', '20101009090715', '0', '1']], 'X-RHN-Auth-User-Id': '', 'X-RHN-Auth-Expire-Offset': '3600.0'}
[Tue Oct 12 10:57:54 2010] up2date D: handle_action {'action': "<?xml version='1.0'?>\n<methodCall>\n<methodName>kickstart.initiate</methodName>\n<params>\n<param>\n<value><string>ibm-hs22-05.rhts.eng.brq.redhat.com</string></value>\n</param>\n<param>\n<value><string>spacewalk-koan</string></value>\n</param>\n<param>\n<value><string> </string></value>\n</param>\n<param>\n<value><string></string></value>\n</param>\n<param>\n<value><string>smqe-ws02.lab.eng.brq.redhat.com:1</string></value>\n</param>\n<param>\n<value><array><data>\n</data></array></value>\n</param>\n</params>\n</methodCall>\n", 'version': 2, 'id': 164}
[Tue Oct 12 10:57:54 2010] up2date D: handle_action actionid = 164, version = 2
[Tue Oct 12 10:57:54 2010] up2date D: do_call kickstart.initiate ('ibm-hs22-05.rhts.eng.brq.redhat.com', 'spacewalk-koan', ' ', '', 'smqe-ws02.lab.eng.brq.redhat.com:1', []) {'cache_only': None}
[Tue Oct 12 10:57:54 2010] up2date
Traceback (most recent call last):
  File "/usr/sbin/rhn_check", line 332, in __run_action
    (status, message, data) = CheckCli.__do_call(method, params, kwargs)
  File "/usr/sbin/rhn_check", line 325, in __do_call
    retval = method(*params, **kwargs)
exceptions.TypeError: initiate() got an unexpected keyword argument 'cache_only'

[Tue Oct 12 10:57:54 2010] up2date D: Sending back response ((6,), 'Fatal error in Python code occured', {})
[Tue Oct 12 10:57:54 2010] up2date D: do_call packages.checkNeedUpdate ('rhnsd=1',) {}
[Tue Oct 12 10:57:54 2010] up2date D: local action status:  (0, 'rpm database not modified since last update (or package list recently updated)', {})
[Tue Oct 12 10:57:54 2010] up2date D: rpcServer: Calling XMLRPC registration.welcome_message
---

so the first question - should it be allowed provisioning of the guests (the system marked as "guest" in Satellite) and 
second question - should it failed ? (the cache_only I assume regards to the maintenance window feature)?


Version-Release number of selected component (if applicable):
rhn-client-tools-1.2.7-1.el5
yum-rhn-plugin-1.2.3-1.el5

How reproducible:
1 from 1 attempt of provisioning to rhel6

Steps to Reproduce:
1. register RHEL5 x86_64 system to the sat540 (where rhel6 channel exists with ks tree of x86_64)
2. entitle with Provisioning
3. apply Tools channels (if it's not)
4. prepare a ks tree and do the provisioning 
5. run rhn_check -vvv on client side
6. on error refer to /var/log/up2date
  
Actual results:
error processed to /var/log/up2date - see above

Expected results:
no error , ks -ing should process fine

Additional info: