Bug 1662704

Summary:	Running remote job using SU effective method on RHEL6 Host failed with 'standard in must be a tty' error.
Product:	Red Hat Satellite	Reporter:	Varatharaja Perumal G <vgunasek>
Component:	Remote Execution	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED CANTFIX	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.4.0	CC:	aruzicka, hyu, inecas
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-02 14:36:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Varatharaja Perumal G 2018-12-31 20:50:37 UTC

Description of problem:

When trying to run remote execution jobs on RHEL 6 machines us SU method, we have received "standard in must be a tty, exit status: 1" on the job. 

Version-Release number of selected component (if applicable):
Red Hat Satellite 6.3 and 6.4

How reproducible:


Steps to Reproduce:
1. Give SU password less access to non-root user on the client.
2. Configure Satellite RHEL 6 host configure the profile to use non-root user as an effective user and Effective User Method as SU.
3. Run the remote job.

Actual results:

"standard in must be a tty, exit status: 1"

Expected results:

Should get the output of the command i have executed.

Additional info: