-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
synchronize with use_ssh_args: Jinja expressions kept in 'ansible_ssh_common_args' #222
Comments
@rnowagk Thanks for reporting this issue. With PR ansible/ansible#73708, parameters related to SSH were removed. From my understanding, we need to come up with parameters with synchronize module. |
Akasurde
added
bug
This issue/PR relates to a bug.
verified
This issue has been verified/reproduced by maintainer
labels
Jul 14, 2021
As a workaround stick to Ansible 2.10 and lower. |
Akasurde
added a commit
to Akasurde/ansible.posix
that referenced
this issue
Jul 14, 2021
SSH configuration migrated from Ansible configuration to SSH connection configuration. Make ``synchronize`` understand this. Fixes: ansible-collections#222 Signed-off-by: Abhijeet Kasurde <[email protected]>
@Akasurde Awesome! Fixed the testcase and my real scenario (which is with a dynamic Azure inventory and a lengthy SSH ProxyCommand in the 'ssh_common_args'). |
Akasurde
added a commit
to Akasurde/ansible.posix
that referenced
this issue
Jul 21, 2021
SSH configuration migrated from Ansible configuration to SSH connection configuration. Make ``synchronize`` understand this. Fixes: ansible-collections#222 Signed-off-by: Abhijeet Kasurde <[email protected]>
Akasurde
added a commit
to Akasurde/ansible.posix
that referenced
this issue
Aug 9, 2021
SSH configuration migrated from Ansible configuration to SSH connection configuration. Make ``synchronize`` understand this. Fixes: ansible-collections#222 Signed-off-by: Abhijeet Kasurde <[email protected]>
Akasurde
added a commit
to Akasurde/ansible.posix
that referenced
this issue
Aug 10, 2021
SSH configuration migrated from Ansible configuration to SSH connection configuration. Make ``synchronize`` understand this. Fixes: ansible-collections#222 Signed-off-by: Abhijeet Kasurde <[email protected]>
Akasurde
added a commit
that referenced
this issue
Aug 11, 2021
SSH configuration migrated from Ansible configuration to SSH connection configuration. Make ``synchronize`` understand this. Fixes: #222 Signed-off-by: Abhijeet Kasurde <[email protected]>
1 task
1 task
This was referenced Aug 19, 2022
This was referenced Sep 14, 2022
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY
A play with synchronize and 'use_ssh_args', which is working in ansible-2.8.19 fails now with messages like:
The reported 'cmd' and "ssh: Could not resolve hostname {{: indicates that my 'ansible_ssh_common_args: "{{ssh_key_args}}" is no longer subject to Jinja processing, but passed as is.
ISSUE TYPE
COMPONENT NAME
synchronize
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
CentOS 7.9 on control an managed nodes
STEPS TO REPRODUCE
Configure some Jinja expression in ansible_ssh_common_args and run a 'synchronize_task' with 'use_ssh_args: yes'
EXPECTED RESULTS
A working rsync command, as with ansible-2.8.19:
ACTUAL RESULTS
Fails ultimately with "ssh: Could not resolve hostname {{'; obviously due to a Jinja expression in the rsync command
The text was updated successfully, but these errors were encountered: