Package Details: molecule 2.20.2-3

Git Clone URL: (read-only)
Package Base: molecule
Description: aids in the development and testing of Ansible roles.
Upstream URL:
Licenses: MIT
Submitter: Foxboron
Maintainer: dncrash
Last Packager: dncrash
Votes: 5
Popularity: 0.156929
First Submitted: 2017-07-30 17:00
Last Updated: 2019-09-19 11:22

Latest Comments

1 2 Next › Last »

thumbless commented on 2019-11-14 18:52

After latest update.

Traceback (most recent call last): File "/usr/bin/molecule", line 6, in <module> from import main ModuleNotFoundError: No module named 'molecule'

pacman -Qqo /usr/lib/python3.7/ | yay -S -

AttributeError: 'FlakesChecker' object has no attribute 'CONSTANT' ERROR: InvocationError for command /usr/bin/bash pkg/ (exited with code 1) ____________________ summary ______________________ py2: commands succeeded ERROR: py3: commands failed ==> ERROR: A failure occurred in check().

dncrash commented on 2019-09-25 08:14

@korrat It's still 2.20.2 for me. I tried updating to 2.22 but there are some problems with the python-tree-frormat dependency (I think the one in the AUR is out of date).

korrat commented on 2019-09-23 11:23

@dncrash it works flawlessly now. Thanks for your quick response and sorry for taking so long. One curious thing though: For me molecule --version returns 2.22. Can you reproduce that or is my environment messed up?

@thumbless that's not a problem with the package itself. That's just molecule working as it should. In short it's telling you that you didn't specify any platforms in test/meta/main.yml.

thumbless commented on 2019-09-22 08:37


molecule init role -r test -d docker

molecule test

It fails on

Executing Ansible Lint ....

[701] Role info should contain platforms

Wondering if this is related to the cookiecutter issue? As molecule should be able to run fine with defaults?

dncrash commented on 2019-09-19 11:24

I tried testing but I forgot I had copied the files manually and they were still there so that's why it was working for me... This time I tried cp instead and I hope it really works. Let me know if you still have issues and thanks again for the feedback and help.

korrat commented on 2019-09-19 10:38

Unfortunately it doesn't work yet. It seems that the new line is only supposed to create directories, according to the manpage.

-d, --directory treat all arguments as directory names; create all components of the specified directories

Since the two directories already exist at that point in the build process, the command has no effect.

dncrash commented on 2019-09-19 08:06

Thanks for the feedback. Should be fixed now.

korrat commented on 2019-09-17 12:12

I am unable to use molecule after installing this package. The command molecule init scenario fails with

cookiecutter.exceptions.RepositoryNotFound: A valid repository for "/usr/lib/python3.7/site-packages/molecule/command/init/../../cookiecutter/scenario/driver/docker" could not be found in the following locations:

The directory /usr/lib/python3.7/site-packages/molecule/cookiecutter/ does not exist.

Copying the cookiecutter directory from the extracted sources into /usr/lib/python3.7/site-packages/molecule/ fixes the issue as far as I can tell.

dncrash commented on 2019-07-28 00:15

Updated to 2.20.2.

ainola commented on 2018-11-14 20:10

Foxboron, are you still interested in maintaining this? If so, please update this package as it's several versions out of date.

If you are not, please orphan it so that it can be maintained.