Issue Description:
I encountered an error when running the playbook that caused the task "Gathering Facts" to fail. The error message I received was:
TASK [Gathering Facts] *****
fatal: [default]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: command-line: line 0: Bad configuration option: pubkeyacceptedalgorithms", "unreachable": true}
Steps to Reproduce:
Execute the playbook amazon-ebs.jenkins with the provided configuration.
The playbook fails at the task "Gathering Facts" with the above error message.
Resolution Attempted:
After analyzing the error message, I noticed that the error was caused by the pubkeyacceptedalgorithms configuration option. To resolve the issue, I removed this option from the configuration.
Additionally, I encountered another error during the playbook execution. The error message is as follows:
Issue Description: I encountered an error when running the playbook that caused the task "Gathering Facts" to fail. The error message I received was:
TASK [Gathering Facts] ***** fatal: [default]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: command-line: line 0: Bad configuration option: pubkeyacceptedalgorithms", "unreachable": true}
Steps to Reproduce:
amazon-ebs.jenkins
with the provided configuration.Resolution Attempted: After analyzing the error message, I noticed that the error was caused by the
pubkeyacceptedalgorithms
configuration option. To resolve the issue, I removed this option from the configuration.Additionally, I encountered another error during the playbook execution. The error message is as follows:
TASK [Gathering Facts] ***** fatal: [default]: FAILED! => {"msg": "failed to transfer file to /home/arun/.ansible/tmp/ansible-local-906_x273od6/tmpedzyw_iq ~arun/.ansible/tmp/ansible-tmp-1689085163.023391-911-48271443937713/AnsiballZ_setup.py:\n\nunknown option -- O\r\nusage: scp [-346BCpqrTv] [-c cipher] [-F ssh_config] [-i identity_file]\n [-J destination] [-l limit] [-o ssh_option] [-P port]\n [-S program] source ... target\n"}
Resolution Attempted: To overcome this error, I removed the
--scp-extra-args
option from the playbook.