Scan Facts Playbook Hangs Indefinitely Due to tset Command

[jamesmarshall24]

Issue

Some environments hang indefinitely due to missing terminal in Tower when running these facts playbooks.

Replication

1. Run a playbook against a host with the oracle oem agent in Tower/AWX
2. Wait for the job to complete

Expected

Job finishes

Observed

Job hangs indefinitely

PID Trace on the host:

  ├─sshd -D [email protected],[email protected],aes256-ctr,aes256-cbc,[email protected],aes128-ctr,[email protected],hmac-sha1-et
  │   ├─sshd
  │   │   └─sshd
  │   │       └─sh -c...
  │   │           └─sudo -H -S -n -u root /bin/sh -c ...
  │   │               └─sh -c echo BECOME-SUCCESS-hfyjvwruwzozgfynbrxxybrukfqgskft ; /usr/bin/python /tmp/ansible-tmp-1632758464.7292757-686745-170612301098636/AnsiballZ_scan_services.py
  │   │                   └─python /tmp/ansible-tmp-1632758464.7292757-686745-170612301098636/AnsiballZ_scan_services.py
  │   │                       └─service /sbin/service gcstartup status
  │   │                           └─gcstartup /etc/init.d/gcstartup status
  │   │                               └─su - storacle -c /dba/software/oem/agent_13.5.0.0.0/install/unix/scripts/agentstup status /dba/software/oem/agent_inst storacle &
  │   │                                   └─ksh -c /dba/software/oem/agent_13.5.0.0.0/install/unix/scripts/agentstup status /dba/software/oem/agent_inst storacle &
  │   │                                       └─tset -s -Q

Additional Information

Running the ad-hoc command tset -s -Q targeting the same host results in the ad-hoc job hanging indefinitely as well.

Workaround for scan_facts.yml, adding TERM environment variable in PLAY:

- hosts: all
  environment:
    TERM: 'xterm'
  vars:
    scan_use_checksum: false
    scan_use_recursive: false
  tasks:
[...]