Bug 1423503 - Remote Commands allways fails: Fatal error in Python code occurred [[6]]" (code -1), under CentOS 5 client
Summary: Remote Commands allways fails: Fatal error in Python code occurred [[6]]" (co...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Spacewalk
Classification: Community
Component: Clients
Version: 2.6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jiří Dostál
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space27
TreeView+ depends on / blocked
 
Reported: 2017-02-17 13:17 UTC by Pekka Panula
Modified: 2017-09-28 18:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-23 15:13:19 UTC
Embargoed:


Attachments (Terms of Use)

Description Pekka Panula 2017-02-17 13:17:54 UTC
User-Agent:       Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0
Build Identifier: 

When executing Remote Commands on spacewalk CentOS 5 clients, it allways returns with: Fatal error in Python code occurred [[6]]" (code -1)

Looking from clients /var/log/up2date it shows Invalid Syntax error:
[Fri Feb 17 14:59:45 2017] up2date D: handle_action{'action': "<?xml version='1.0'?>\n<methodCall>\n<methodName>script.run</methodName>\n<params>\n<param>\n<value><int>44250</int></value>\n</param>\n<param>\n<value><struct>\n<member>\n<name>username</name>\n<value><string>root</string></value>\n</member>\n<member>\n<name>groupname</name>\n<value><string>root</string></value>\n</member>\n<member>\n<name>now</name>\n<value><string>2017-02-17 14:58:54</string></value>\n</member>\n<member>\n<name>timeout</name>\n<value><int>600</int></value>\n</member>\n<member>\n<name>script</name>\n<value><string>#!/bin/sh\n# Add your shell script below\nid</string></value>\n</member>\n</struct></value>\n</param>\n</params>\n</methodCall>\n", 'version': 2, 'id': 44250}
[Fri Feb 17 14:59:45 2017] up2date D: handle_action actionid = 44250, version = 2
[Fri Feb 17 14:59:45 2017] up2date D: do_call script.run(44250, {'username': 'root', 'groupname': 'root', 'now': '2017-02-17 14:58:54', 'timeout': 600, 'script': '#!/bin/sh\n# Add your shell script below\nid'}){'cache_only': None}
[Fri Feb 17 14:59:45 2017] up2date 
Traceback (most recent call last):
  File "/usr/sbin/rhn_check", line 381, in __run_action
    (status, message, data) = CheckCli.__do_call(method, params, kwargs)
  File "/usr/sbin/rhn_check", line 373, in __do_call
    method = getMethod.getMethod(method, "/usr/share/rhn/", "actions")
  File "/usr/share/rhn/up2date_client/getMethod.py", line 83, in getMethod
    actions = __import__(modulename)
exceptions.SyntaxError: invalid syntax (script.py, line 52)

[Fri Feb 17 14:59:45 2017] up2date D: Sending back response((6,), 'Fatal error in Python code occurred', {})

Same remote command under CentOS 6 and 7 runs ok without errors.

Reproducible: Didn't try




Spacewalk server is installed on CentOS 7.3, and uses Spacewalk v2.6 repository. 

Clients are CentOS 5/6/7 versions and only CentOS 5.x spacewalk clients gives this error. I tested to run Remote Command on CentOS 6 and CentOS 7 and they run ok.

CentOS 5 spacewalk client RPM versions:
spacewalk-client-repo-2.6-0.el5
spacewalk-backend-usix-2.6.75-1.el5
rhn-org-trusted-ssl-cert-1.0-1
rhncfg-5.10.99-1.el5
rhncfg-actions-5.10.99-1.el5
rhn-setup-2.6.8-1.el5
rhnlib-2.6.3-1.el5
rhncfg-client-5.10.99-1.el5
yum-rhn-plugin-2.6.3-1.el5
rhn-check-2.6.8-1.el5
rhn-client-tools-2.6.8-1.el5
rhnsd-5.0.25-1.el5

Comment 1 Jiří Dostál 2017-02-23 15:13:19 UTC
Hello, this issue is already fixed by commit 0acf2fb7295a42e791c42f7191367b3b645900b7 in version rhncfg-5.10.100-1.
Closing - reopen if disagree

Comment 2 Eric Herget 2017-09-28 18:09:45 UTC
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.


Note You need to log in before you can comment on or make changes to this bug.