Closed isuftin closed 2 years ago
It looks like when I change ssh_connection
to ssh
and retries
to reconnection_retries
, this works fine.
provisioner:
name: ansible
log: True
config_options:
defaults:
bin_ansible_callbacks: True
callbacks_enabled: ${ANSIBLE_CALLBACKS}
display_args_to_stdout: True
pipelining: True
show_custom_stats: True
stdout_callback: ${ANSIBLE_STDOUT_CALLBACK}
timeout: ${ANSIBLE_CONNECTION_TIMEOUT}
use_persistent_connections: True
verbosity: ${ANSIBLE_STDOUT_VERBOSITY}
fact_caching: jsonfile
fact_caching_connection: ${MOLECULE_EPHEMERAL_DIRECTORY}/facts_cache
fact_caching_timeout: 7200
diff:
always: True
galaxy:
display_progress: False
ssh:
ssh_args: ${SSH_ARGS}
reconnection_retries: ${SSH_RETRIES}
@isuftin it looks like the pipelining issue was fixed for me, but ssh_args
did not do the trick, I think it's no longer being read/parsed.
I'm attempting to workaround with this :)
https://github.com/vexxhost/atmosphere/commit/c5e4ff2f62e5d7dd6a443e8b5df34e9f6554f9c4
Issue Type
Molecule and Ansible details
Molecule installation method (one of): pip
Ansible installation method (one of): pip
Detail any linters or test runners used:
Desired Behavior
No configuration errors
Actual Behaviour
With Molecule 4.0.3, I am seeing an error coming back which I haven't seen in previous versions:
config.yml:
senario YAML:
If I comment out the
ssh_connection
params under provisioner, this works fine. However, I thought that this was valid configuration as per https://github.com/ansible/ansible/blob/5037dc4e69b140a2f5345711fe9318d3fdea730e/lib/ansible/constants.py#L300-L304Am I doing it wrong or is this a regression in Molecule in 4.0.3?