Bug 951243

Summary:	[RFE] log the remote command results on the machine that runs them
Product:	[Community] Spacewalk	Reporter:	Grant Gainey <ggainey>
Component:	Clients	Assignee:	Grant Gainey <ggainey>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.10	CC:	adellape, cperry, ggainey, jwest, tao, tkasparek
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	rhncfg-5.10.46-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	579885	Environment:
Last Closed:	2013-08-02 13:02:34 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:	579885
Bug Blocks:	991452

Description Grant Gainey 2013-04-11 18:36:41 UTC

There are no logs of the remote commands execution on the machine that
execute them

3) Business Requirements Satisfied By Request:
being able to get these logs from the machine, not only spacewalk

4) Functional Requirements That Are Not Presently Possible:
those logs are only present in spacewalk

5) What Will Success Look Like:
a new log file holding the results will be created on the machine with
details that would otherwise be available from spacewalk

Comment 1 Grant Gainey 2013-04-11 19:11:31 UTC

Implementing this would mean that the output of scripts run as root would end up on the client-machine's drive. There are some security and disk-space issues that come to mind.

To give the admin of the client-machine (as possibly separate from the spacewalk-admin that can arrange for remote-cmds to run on the client) more control of the impacts to their machine, propose adding two new settings to

/etc/sysconfig/rhn/rhncfg-client.conf :

script_log_file = /var/log/rhn/rhncfg-actions.log

script_log_file_enable = 1

If script_log_file_enable = 0, we don't log on the client.

script_log_file should have 600 perms for root, only.

Comment 2 Grant Gainey 2013-04-12 13:50:37 UTC

spacewalk commit 9f89d22a515a710ceaadd475a000d3827061c2ae

Comment 4 Tomáš Kašpárek 2013-08-02 13:02:34 UTC

Fix for this bug is present in Spacewalk 2.0, closing this bug as CURRENTRELEASE.