Molecule test

[dj-wasabi]

Adding molecule tests and removing test-kitchen tests.

[retr0h]

@dj-wasabi looking into your failure. I thought we fixed this, it was a bug that occurs with ansible 2.1.1.

[dj-wasabi]

Hi @retr0h I have on my local machine molecule 1.9.0 and Ansible 2.1.1.0 installed and there it works...

[retr0h]

Hi @retr0h I have on my local machine molecule 1.9.0 and Ansible 2.1.1.0 installed and there it works...

Do you have a custom ansible.cfg on your local system that could be changing the path to where it finds the roles? I'm trying to hunt down the source of the problem.

Also, my apologies for causing issues. Was hoping 1.9 would be a seamless upgrade.

[retr0h]

While, I am working on a fix, you will also want to update your testinfra tests with this.

molecule init adds these to the tests created, however, you have tests created pre-1.9. This will allow you to target groups which the vagrant backend would let you do. Unfortunately is a limitation of testinfra's docker backend.

[retr0h]

@dj-wasabi While I fix molecule you can update your molecule.yml with the following. This should work-a-round the issue for now.

ansible:
  raw_env_vars:
    ANSIBLE_ROLES_PATH: .molecule/roles:../.molecule/roles:../:../../

[dj-wasabi]

@retr0h

No worries mate ;-)

I only have the one in the root of this repository which is the one called from molecule.yml:

[defaults]
roles_path = ../:../../
hostfile = tests/inventory

It worked locally, because the roles where already found in the roles_path. I deleted the dependency roles and now I get the same error as on Travis.

But when running the molecule converge step locally doesn't download the roles, but it did on travis..

[retr0h]

Don't forget to update your tests as I indicated in a few comments above, and you should be green.

[dj-wasabi]

Yes, I see it. (Sorry, I've already created an issue for this. Will close it.)

Thank you!

[retr0h]

I believe I fixed the issues you ran into. 1.9.1 was pushed to pypi.

[dj-wasabi]

@retr0h Thanks again!