Bug 1662704 - Running remote job using SU effective method on RHEL6 Host failed with 'standard in must be a tty' error.
Summary: Running remote job using SU effective method on RHEL6 Host failed with 'stand...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.4.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-31 20:50 UTC by Varatharaja Perumal G
Modified: 2022-03-13 16:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-02 14:36:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1429819 0 medium CLOSED If some command in the job template reads from STDIN the job never finishes 2021-02-22 00:41:40 UTC

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:
Note You need to log in before you can comment on or make changes to this bug.