Skip to content
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

Missing ansible_ssh_common_args form ansible_inventory.yml using managed delegated driver #2859

Closed
H0neyBadger opened this issue Oct 5, 2020 · 0 comments · Fixed by #3121
Labels

Comments

@H0neyBadger
Copy link

Issue Type

  • Bug report

Molecule and Ansible details

ansible 2.10.1
  config file = None
  configured module search path = ['/home/redacted/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = redacted
  executable location = redacted
  python version = 3.6.8 (default, Apr 16 2020, 01:36:27) [GCC 8.3.1 20191121 (Red Hat 8.3.1-5)]
molecule 3.0.8
   ansible==2.10.1 python==3.6

Molecule installation method (one of):

  • pip

Ansible installation method (one of):

  • pip

Detail any linters or test runners used:

Desired Behavior

override ssh_config in with delegated managed configuration
~/.cache/molecule/project/default/inventory/ansible_inventory.yml

Actual Behaviour

I tried many combination of options, but I'm still not able to override the default ssh client behavior.

driver:
  name: delegated
  options:
    managed: true
    ansible_connection_options:
      ansible_ssh_common_args: '-F /tmp/ssh_config'

when managed: false -> the create.yml is never run
when managed: true -> the ansible_ssh_common_args is ignored

after long hours of troubleshoot. the _get_instance_config does not seems to detect my instance_config. My instance_config.yml produced by create.yml earlier looks correct however.
#1292 (comment)

I created my molecule template using the following command

molecule init scenario --driver-name=delegated --verifier-name=ansible

I do not know what am I supposed to do. My initial problem is that the verify command fail because of error Name or service not known (that's normal since the platform name is not known in our infra).
Creating an ssh config is error prone, the ansible_host do the job usually. but I m running out of idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant