When executing the rhui-manager status command, the following error is output and service information cannot be obtained.

Solution In Progress - Updated -

Issue

When executing the rhui-manager status command, the following error is output and service information cannot be obtained.

# rhui-manager status
<snip>
Services status

An unexpected error has occurred during the last operation.

Encountered a bad command exit code!

Command: 'ansible-playbook -i /tmp/tmp6icu0poe /usr/share/rhui-tools/playbooks/rhui-manager_status.yml'

Exit code: 4

Stdout:

fatal: [cds1.rhui-exam.local]: UNREACHABLE! => {"changed": false, "msg": "Failed to create temporary directory. In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in \"/tmp\", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p \"` echo ~/.ansible/tmp `\"&& mkdir \"` echo ~/.ansible/tmp/ansible-tmp-1699929765.45036-57028-164689307304783 `\" && echo ansible-tmp-1699929765.45036-57028-164689307304783=\"` echo ~/.ansible/tmp/ansible-tmp-1699929765.45036-57028-164689307304783 `\" ), exited with result 1", "unreachable": true}
fatal: [cds2.rhui-exam.local]: UNREACHABLE! => {"changed": false, "msg": "Failed to create temporary directory. In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in \"/tmp\", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p \"` echo ~/.ansible/tmp `\"&& mkdir \"` echo ~/.ansible/tmp/ansible-tmp-1699929765.4582503-57029-224940010538390 `\" && echo ansible-tmp-1699929765.4582503-57029-224940010538390=\"` echo ~/.ansible/tmp/ansible-tmp-1699929765.4582503-57029-224940010538390 `\" ), exited with result 1", "unreachable": true}
fatal: [cds3.rhui-exam.local]: UNREACHABLE! => {"changed": false, "msg": "Failed to create temporary directory. In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in \"/tmp\", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p \"` echo ~/.ansible/tmp `\"&& mkdir \"` echo ~/.ansible/tmp/ansible-tmp-1699929765.475374-57030-71354176325823 `\" && echo ansible-tmp-1699929765.475374-57030-71354176325823=\"` echo ~/.ansible/tmp/ansible-tmp-1699929765.475374-57030-71354176325823 `\" ), exited with result 1", "unreachable": true}

PLAY RECAP *********************************************************************
cds1.rhui-exam.local : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0   
cds2.rhui-exam.local : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0   
cds3.rhui-exam.local : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0   
localhost                  : ok=3    changed=2    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   

Stderr:

Environment

Red Hat Update Infrastructure 4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content