Created attachment 359014 [details] catalina.out Description of problem: I'm getting ISE when trying to schedule KS. Version-Release number of selected component (if applicable): 20080920.0 How reproducible: always Steps to Reproduce: 1. Create KS 2. Try to schedule that KS Actual results: ISE and traceback in catalina.out Expected results: should just work Additional info: This satellite is synced against WebQA. I'm going to try to re-sync to see if it is a problem with data.
Also I see this inthe cobblerd.log: 2009-08-31 09:00:16,828 - api - login attempt; user(admin) 2009-08-31 09:00:16,828 - api - authenticate; ['admin', False] 2009-08-31 09:00:16,829 - api - login failed; user(admin) 2009-08-31 09:00:16,829 - api - Exception occured: cobbler.cexceptions.CX 2009-08-31 09:00:16,829 - api - Exception value: 'login failed: admin' 2009-08-31 09:00:16,829 - api - Exception Info: File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 1567, in _dispatch return method_handle(*params) File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 1033, in login raise CX(_("login failed: %s") % login_user)
# cat /etc/cobbler/users.digest cobbler:Cobbler:a2d6bae81669d707b72c0bd9806e01f3
# cobbler aclsetup --adduser=admin - setfacl -d -R -m u:admin:rwx /var/www/cobbler setfacl: Option -m: Invalid argument near character 3 command failed
OK, I have changed: # diff -u /usr/lib/python2.4/site-packages/cobbler/api.py{.ORIG,} --- /usr/lib/python2.4/site-packages/cobbler/api.py.ORIG 2009-08-31 09:43:25.000000000 +0200 +++ /usr/lib/python2.4/site-packages/cobbler/api.py 2009-08-31 09:43:40.000000000 +0200 @@ -667,7 +667,8 @@ """ rc = self.authn.authenticate(self,user,password) self.log("authenticate",[user,rc]) - return rc + ###return rc + return True def authorize(self,user,resource,arg1=None,arg2=None): """ And now I can see list of the kickstarts. But still, when I want to KS my system, cobblerd.log shows (I have also reacivated the system: Details -> Reactivation -> rhnreg_ks...): 2009-08-31 09:49:32,270 - api - calling authorize for resource ['new_system', None, None]; user(jhutar) 2009-08-31 09:49:32,270 - api - authorization result: True; user(?) 2009-08-31 09:49:32,274 - api - calling authorize for resource ['modify_system', <cobbler.item_system.System instance at 0x3cfc050>, 'name']; user (jhutar) 2009-08-31 09:49:32,275 - api - authorization result: True; user(?) 2009-08-31 09:49:32,275 - api - Exception occured: cobbler.cexceptions.CX 2009-08-31 09:49:32,275 - api - Exception value: 'invalid characters in name: (' 2009-08-31 09:49:32,275 - api - Exception Info: File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 1567, in _dispatch return method_handle(*params) File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 1401, in modify_system return self.__call_method(obj, attribute, arg) File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 1374, in __call_method return method(arg) File "/usr/lib/python2.4/site-packages/cobbler/item_system.py", line 325, in set_name raise CX(_("invalid characters in name: %s") % x) And my system's profilename is "MAT (dhcp-lab-126.englab.brq.redhat.com)", so this might be the cause. So, maybe this is for 2 bugs: 1. satellite users can not authenticate to the cobblerd => somebody who knows how satellite manages cobbler users, should check everithing is OK (this might be a NOTABUG, as I have the satellite on the system where I had multiple older nightlies and everytime just removed DB and uninstalled all satellite packages) 2. although satellite allows me to use "(" char in the profilename, cobbler do nt like that => could anybody with clean satellite install verify this?
Justin can you take a review of this bug and determine how critical/urgent it is. If it can wait for 531 (or beyond) or needs attention sooner. Thanks, Cliff
jan, can you point me to a reproducer? I see the client, but not the spacewalk server. Thanks!
Actually nevermind, I easily recreated it :}
This should have been fixed and released as part of RHBA-2009:1566. Going to go ahead and close. *** This bug has been marked as a duplicate of bug 531059 ***