private_key_file created twice in asnible.config about ansible HOT 6 CLOSED

Files identified in the description:

• bin/ansible-config

If these files are incorrect, please update the component name section of the description or use the component bot command.

from ansible.

@risadams ansible-core 2.14 is not supported and no longer receives bug fixes. Please test against one of the supported versions of ansible-core, preferably the most recent one, to see whether the bug has been fixed.

click here for bot help

from ansible.

Duplicate of the resolved #82481

from ansible.

~$ ansible --version
ansible [core 2.16.4]
...
~$ ANSIBLE_VERBOSITY= ansible-config init --disabled -t all > /tmp/ansible.cfg
~$ grep -E '^\[|private_key_file' /tmp/ansible.cfg 
[defaults]
;private_key_file=
[privilege_escalation]
[persistent_connection]
[connection]
[colors]
[selinux]
[diff]
[galaxy]
[inventory]
[netconf_connection]
[paramiko_connection]
;private_key_file=
[jinja2]
[tags]
[runas_become_plugin]
[su_become_plugin]
[sudo_become_plugin]
[callback_tree]
[ssh_connection]
[winrm]
[inventory_plugins]
[inventory_plugin_script]
[inventory_plugin_yaml]
[url_lookup]
[powershell]
[vars_host_group_vars]

from ansible.

Closing as per above.

If you have further questions please stop by IRC or the mailing list:

• IRC: #ansible on irc.libera.chat
• mailing list: https://groups.google.com/forum/#!forum/ansible-project

See this page for a complete and up to date list of communication channels and their purposes:

• https://docs.ansible.com/ansible/latest/community/communication.html

from ansible.

@sivel (et, all)
Thank you very much, I missed that ticket when looking for duplicates.

from ansible.