network_cli ignores environmental var TERM to establish ssh connection (Linux RHEL 8.9)

[Azadeh2018]

SUMMARY

target hostname is a cisco ios-xr device and as configured it supports vt100 as its terminal emulator. When playbook which utilizes network_cli as its connection is executed, the end device generates a warning: The requested term-type 'xterm' is not supported. Although the environmental var TERM is set to vt100 via 'export TERM=vt100'

ISSUE TYPE

• when in playbook network_cli is used, you cannot force it to consider vt100 as the host's terminal emulator

COMPONENT NAME

ansible.netcommon 7.0.0

ANSIBLE VERSION

$ ansible --version
ansible [core 2.16.7]
config file = /home/ansible/.ansible.cfg
configured module search path = ['/home/ansible/library']
ansible python module location = /usr/local/lib/python3.11/site-packages/ansible
ansible collection location = /home/ansible/collections
executable location = /usr/local/bin/ansible
python version = 3.11.7 (main, Jan 26 2024, 15:26:41) [GCC 8.5.0 20210514 (Red Hat 8.5.0-21)] (/bin/python3.11)
jinja version = 3.1.4
libyaml = True

##### COLLECTION VERSION
ansible.netcommon 7.0.0
cisco.iosxr 10.0.0

CONFIGURATION

OS / ENVIRONMENT

Red HAt Enterprise Linux release 8.9 (Ootpa)

EXPECTED RESULTS

how to have network_cli to consider environment variableTERM value or somehow have it work with vt100 in place of xterm as its terminal emulator

[j498060]

Can someone clarify which ‘Terminal Type’ is defined in this module when using network_cli as the connection? Does it support ‘vt100’ as the Terminal Type overall?