ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Use exports (#23542)

Browse source
This commit is contained in:
John R Barker 2017-04-12 16:03:31 -04:00 committed by GitHub
parent 38eed2dab0
commit 729b0e3bee
1 changed files with 11 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
docs/docsite/rst/network_debug_troubleshooting.rst
View file

@ -55,9 +55,11 @@ Because logging is very verbose it is disabled by default. It can be enabled via
# Specify the location for the log file
export ANSIBLE_LOG_PATH=~/ansible.log
# Enable Debug
export ANSIBLE_DEBUG=True
# Run with 4*v for connection level verbosity
ANSIBLE_DEBUG=True ansible-playbook -vvvv ...
ansible-playbook -vvvv ...
After Ansible has finished running you can inspect the log file:
@ -122,10 +124,12 @@ If you have SSH keys configured correctly you can drop the ``-k`` parameter
If the connection still fails you can combine it the enable_network_logging_, for example::
# Specify the location for the log file
export ANSIBLE_LOG_PATH=~/ansible.log
# Run with 4*v for connection level verbosity
ANSIBLE_DEBUG=True ansible -m eos_command -a 'commands=?' -i inventory switch1.example.net -e 'ansible_connection=local' -u admin -k
# Specify the location for the log file
export ANSIBLE_LOG_PATH=~/ansible.log
# Enable Debug
export ANSIBLE_DEBUG=True
# Run with 4*v for connection level verbosity
ansible -m eos_command -a 'commands=?' -i inventory switch1.example.net -e 'ansible_connection=local' -u admin -k
Then review the log file and find the relevant error message in the rest of this document.
@ -268,7 +272,8 @@ You can tell Ansible to automatically accept the keys
Environment variable method::
ANSIBLE_PARAMIKO_HOST_KEY_AUTO_ADD=True ansible-playbook ...
export ANSIBLE_PARAMIKO_HOST_KEY_AUTO_ADD=True
ansible-playbook ...
``ansible.cfg`` method: