Closed ysebastia closed 1 year ago
Same problem here. I downgraded to 5.0.1 and things backed to work again.
I'm not sure why this new version broke the vagrant plugin. Fortunately, a similar error was reported to the plugin some time ago and got fixed. So, I guess it should be working with molecule-plugins git HEAD.
I'm using molecule with vagrant plugin, according to "ModuleNotFoundError: No module named 'ansible.module_utils.common.yaml'" it seems like some ansible module(s) could be missing. This environment is quite basic venv with latest ansible and setuptools. I can also confirm that reverting back to 5.0.1 overcomes the issue.
More verbose error below:
fatal: [localhost]: FAILED! => {
"changed": false,
"module_stderr": "ansible-config [core 2.15.2]\n config file = /home/.../ansible.cfg\n configured module search path = ['/home/.../venv/lib64/python3.11/site-packages/molecule/provisioner/ansible/plugins/modules', '/home/.../venv/lib64/python3.11/site-packages/molecule_plugins/vagrant/modules', '/home/.../.cache/molecule/myproject/default/library', '/home/.../myproject/library', '/home/.../.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']\n ansible python module location = /home/.../venv/lib64/python3.11/site-packages/ansible\n ansible collection location = /home/.../.cache/ansible-compat/57c36d/collections:/home/.../.cache/molecule/myproject/default/collections:/home/.../.ansible/collections:/usr/share/ansible/collections:/etc/ansible/collections\n executable location = /home/.../venv/bin/ansible-config\n python version = 3.11.4 (main, Jun 7 2023, 00:00:00) [GCC 13.1.1 20230511 (Red Hat 13.1.1-2)] (/home/.../venv/bin/python3)\n jinja version = 3.1.2\n libyaml = True\nUsing /home/.../.cache/molecule/myproject/default/ansible.cfg as config file\nTraceback (most recent call last):\n File \"/home/.../.ansible/tmp/ansible-tmp-1691067206.2547-27981-1954710112728/AnsiballZ_vagrant.py\", line 107, in <module>\n _ansiballz_main()\n File \"/home/.../.ansible/tmp/ansible-tmp-1691067206.2547-27981-1954710112728/AnsiballZ_vagrant.py\", line 99, in _ansiballz_main\n invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n File \"/home/.../.ansible/tmp/ansible-tmp-1691067206.2547-27981-1954710112728/AnsiballZ_vagrant.py\", line 47, in invoke_module\n runpy.run_module(mod_name='ansible.modules.vagrant', init_globals=dict(_module_fqn='ansible.modules.vagrant', _modlib_path=modlib_path),\n File \"<frozen runpy>\", line 226, in run_module\n File \"<frozen runpy>\", line 98, in _run_module_code\n File \"<frozen runpy>\", line 88, in _run_code\n File \"/tmp/ansible_vagrant_payload_mtknx84z/ansible_vagrant_payload.zip/ansible/modules/vagrant.py\", line 33, in <module>\n File \"/home/.../venv/lib64/python3.11/site-packages/molecule/util.py\", line 40, in <module>\n from molecule.app import app\n File \"/home/.../venv/lib64/python3.11/site-packages/molecule/app.py\", line 13, in <module>\n app = App()\n ^^^^^\n File \"/home/.../venv/lib64/python3.11/site-packages/molecule/app.py\", line 10, in __init__\n self.runtime = Runtime(isolated=True)\n ^^^^^^^^^^^^^^^^^^^^^^\n File \"/home/.../venv/lib64/python3.11/site-packages/ansible_compat/runtime.py\", line 213, in __init__\n from ansible.utils.display import Display\n File \"/home/.../venv/lib64/python3.11/site-packages/ansible/utils/display.py\", line 49, in <module>\n from ansible import constants as C\n File \"/home/.../venv/lib64/python3.11/site-packages/ansible/constants.py\", line 12, in <module>\n from ansible.config.manager import ConfigManager\n File \"/home/.../venv/lib64/python3.11/site-packages/ansible/config/manager.py\", line 21, in <module>\n from ansible.module_utils.common.yaml import yaml_load\nModuleNotFoundError: No module named 'ansible.module_utils.common.yaml'\n",
"module_stdout": "",
"msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",
"rc": 1
}
Hello, everything works fine with molecule-plugins v23.5.0 :)
@jimboolio I am also facing the same issue with the vagrant plugin
Issue Type
Molecule and Ansible details
Molecule installation method :
Ansible installation method :
Desired Behavior
Molecule should run.
Actual Behaviour
Before update, Molecule 5.0.1 works great :
After update to Molecule 5.10 (and ansible-compat 4.1.2 by the way), Molecule do not work anymore :
This is my
.config/molecule/config.yml
file configuration :Output of running with
molecule --debug
:The failure is strange because the file
~/molecule5.1.0/lib64/python3.11/site-packages/ansible/module_utils/common/yaml.py
exists.