molecule broken with latest version of ansible-compat
#3903
Comments
ansible/molecule#3903 Signed-off-by: Rick Elrod <[email protected]>
|
+1 , just ran into it. |
|
Btw. do the dependencies work as expected for us here? https://github.com/ansible-community/molecule/tree/main/.config Looks like we should be locked to |
|
i have the same issue : i have molecule v 5.0.0 with poython v 3.10 , absible core 2.14.5 , when i try to create new ansible role i got this error: |
Molecule doesn't support latest version of ansible-compat so we need to pin it (ref: ansible/molecule#3903). Signed-off-by: Arthur Outhenin-Chalandre <[email protected]>
ansible/molecule#3903 Signed-off-by: Rick Elrod <[email protected]>
Molecule doesn't support latest version of ansible-compat so we need to pin it (ref: ansible/molecule#3903). Signed-off-by: Arthur Outhenin-Chalandre <[email protected]>
Due to an issue introduced on newer ansible-compat and molecule (see ansible/molecule#3903), ansible-compat needs to be pinned to an older version.
Due to an issue introduced on newer ansible-compat and molecule (see ansible/molecule#3903), ansible-compat needs to be pinned to an older version.
This is necessary because version 4 of this package contains a breaking change that causes Molecule to fail right out of the box. See ansible/molecule/issues/3903 for more details.
As described in ansible/molecule#3903 the latest updates in ansible-compat are breaking molecule. While waiting for the proper fix, let's just pin things up.
|
Reverting from ansible-compat 4.0.1 to 3.0.2 fixed the issue for me. |
ansible/molecule#3903 Signed-off-by: Rick Elrod <[email protected]>
Upstream bug caused Molecule to not be able to run in our CI flows. ansible/molecule#3903
Upstream bug caused Molecule to not be able to run in our CI flows. ansible/molecule#3903
Upstream bug caused Molecule to not be able to run in our CI flows. ansible/molecule#3903
Upstream bug caused Molecule to not be able to run in our CI flows. ansible/molecule#3903
Explicitly installs a molecule version with fix for ansible/molecule#3903 to run tests.
Install a version of molecule with a fix for ansible/molecule#3903
|
The problem popped up again and many people will likely get hit by this due to the latest version of This means that even with Molecule 5.0.1 released, many people will run into this issue, and you need manual intervention to fix this. |
Molecule and ansible-lint require ansible-compat in different versions and installing both currently breaks molecule (again). This patchremoves ansible-lint from the Molecule workflow since we don't need it in there anyway. We have a separate workflow for that. More details: ansible/molecule#3903 (comment)
Molecule and ansible-lint require ansible-compat in different versions and installing both currently breaks molecule (again). This patchremoves ansible-lint from the Molecule workflow since we don't need it in there anyway. We have a separate workflow for that. More details: ansible/molecule#3903 (comment)
|
#3904 will fix it finally for good. |
* Use run, not exec, for ansible-compat 4.0.2 4.0.2 dropped the use of `exec`, needs to be replaced with `run` Fixes #3903 ansible/ansible-compat#256 * bump ansible-compat 4.1.2 ansible-compat 4.0.1 included a breaking change. If we want to use latest, minimum version must be at least 4.0.1. ansible-compat < 4.1.2 has an issue that causes an unhandled exception for certain log levels. ansible/ansible-lint#3522 Since this issue caused CI trouble, we go ahead and bump to 4.1.2. * fixup * [DATALAD RUNCMD] recompile requirements.lock.txt === Do not change lines below === { "chain": [], "cmd": "pip-compile --no-annotate --output-file=.config/requirements-lock.txt --resolver=backtracking --strip-extras --unsafe-package=ruamel-yaml-clib pyproject.toml", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^ * fix tests for command init role and init scenario Currently the tests fail for `test_command_init_role` and `test_command_init_scneario`. The tests execute `ansible-lint` on the newly-created roles and the linter recently got more restrictive, so we now have to adapt. * [DATALAD RUNCMD] recompile requirements.txt === Do not change lines below === { "chain": [], "cmd": "pip-compile --extra=docs --extra=test --no-annotate --output-file=.config/requirements.txt --resolver=backtracking --strip-extras pyproject.toml", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^ * Fake 3.9 for autogenerated files I used 3.10, but CI will run this on 3.9, and fail if there is a diff. This means it is safe to change this by hand, since it will be checked. --------- Co-authored-by: Daniel Ziegenberg <[email protected]>
|
Is there any fix in the meantime? |
|
You can just install Molecule 5.0.1 specifically. Pip will then resole the modules and install an older version of ansible-lint: |
ansible/molecule#3903 - this removes the ability to use `molecule lint` command
molecule is failing with this error ansible/molecule#3903 the ability to run `molecule lint` is no longer possible
* remove the failing AGENT tools directory. the variable is not used * updating to new molecule version molecule is failing with this error ansible/molecule#3903 the ability to run `molecule lint` is no longer possible
* Use set when have many acls to speedup checks * Downgrade ansible-compat test lib see ansible/molecule#3903
Issue Type
Molecule and Ansible details
Molecule installation method (one of):
Ansible installation method (one of):
Detail any linters or test runners used:
Desired Behavior
molecule testshould successfully perform testing.Actual Behaviour
This is likely caused by https://github.com/ansible-community/molecule/blob/0d874bd9ccacda8df5e110020454764a6b9b908d/src/molecule/util.py#L149 not being updated for ansible/ansible-compat#256 which was included in ansible-compat v4.0.1.
The text was updated successfully, but these errors were encountered: