Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 516113

Summary:	Remote commands via Satellite fails with meaningless error message
Product:	[Community] Spacewalk	Reporter:	Xixi <xdmoon>
Component:	Server	Assignee:	Jesus M. Rodriguez <jesusr>
Status:	CLOSED DUPLICATE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	0.5	CC:	agouny, bishop, cperry, jsherril, tao, xdmoon
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	493380
Clones:	613998 (view as bug list)		Environment:
Last Closed:	2010-02-16 05:37:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	582354, 613998

Comment 1 Xixi 2009-08-06 19:38:33 UTC

Public bug description:

Error message generated when attempting to send remote commands from
satellite to hosts with remote actions not enabled (via "rhn-actions-control --enable-run") generates ambiguous error message:
"Client execution returned "Invalid function call attempted" (code 6)"

The error message should say what is wrong in more meaningful terms, so that corrective action can easily be taken.  So instead of "Invalid function call attempted" (code 6)" we should write in event history log, something like:
"  Host has disabled ability to run remote scripts. Please run 
  rhn-actions-control --enable-run
  on targeted host to enable this ability."

Comment 2 Aurelien Gouny 2010-02-16 05:37:17 UTC


*** This bug has been marked as a duplicate of bug 437824 ***

Comment 3 Bishop Clark 2018-05-11 17:33:07 UTC

This ticket has been closed as a duplicate of a restricted bug, with no other comments.

Is there anything we can learn from this hidden ticket?