Bug 2028285

Summary: tracer hangs forever if not ran via tty
Product: Red Hat Satellite Reporter: jcallaha
Component: katello-tracerAssignee: satellite6-bugs <satellite6-bugs>
Status: NEW --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: high    
Version: 6.10.1CC: chrobert, jkadlcik
Target Milestone: UnspecifiedKeywords: AutomationBlocker, TestBlocker, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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 jcallaha 2021-12-01 22:04:14 UTC 
Description of problem:
tracer performs a check to see if it can expect additional input from stdin, if so then it tries to read from stdin
https://github.com/FrostyX/tracer/blob/master/tracer/main.py#L42
However, this conditional also triggers if you run tracer via a non-tty ssh method. tracer then hangs on the blocking read until the session is killed.

Version-Release number of selected component (if applicable):
All versions. This part of the codebase has been intact for at least 7 years.

How reproducible:
100%

Steps to Reproduce:
1. Install tracer on a host
2. ssh root@<your host> tracer

Actual results:
The ssh command will continue to wait until killed (or timed out by other means)

Expected results:
tracer runs as normal (with a better mechanism of checking the stdin buffer)

Additional info:
os.isatty(0) also has the same issue
Comment 2 Brad Buckingham 2023-07-21 21:06:39 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.