Unknown command: ansible-playbook

[mathias-ioki]

Prerequisites

• This was not already reported in the past (duplicate check)
• It does reproduce it with code from main branch (latest unreleased version)
• I include a minimal example for reproducing the bug
• The bug is not trivial, as for those a direct pull-request is preferred
• Running pip check does not report any conflicts
• I was able to reproduce the issue on a different machine
• The issue is not specific to any driver other than 'default' one

Environment

molecule 6.0.3 using python 3.11
    ansible:2.16.2
    azure:23.5.0 from molecule_plugins
    containers:23.5.0 from molecule_plugins requiring collections: ansible.posix>=1.3.0 community.docker>=1.9.1 containers.podman>=1.8.1
    default:6.0.3 from molecule
    docker:23.5.0 from molecule_plugins requiring collections: community.docker>=3.0.2 ansible.posix>=1.4.0
    ec2:23.5.0 from molecule_plugins
    gce:23.5.0 from molecule_plugins requiring collections: google.cloud>=1.0.2 community.crypto>=1.8.0
    podman:23.5.0 from molecule_plugins requiring collections: containers.podman>=1.7.0 ansible.posix>=1.3.0
    vagrant:23.5.0 from molecule_plugins

What happened

I've installed latest molecule and latest molecule-plugins to the same virtual env. Also all the ansible packages are installed to this virtual environment.

Trying to initialize a new scenario will throw an exception that the ansible-playbook command can't be found:

> pipenv shell
> molecule init scenario
INFO     Initializing new scenario default...
fish: Unknown command: ansible-playbook
fish:
ansible-playbook -i localhost, --connection=local --extra-vars '{"dependency_name": "galaxy", "driver_name": "default", "provisioner_name": "ansible", "scenario_name": "default", "subcommand": "molecule.command.init.scenario"}' /Users/myuser/.local/share/virtualenvs/ansible-6KFbR7gx/lib/python3.11/site-packages/molecule/data/init-scenario.yml
^~~~~~~~~~~~~~~^
Traceback (most recent call last):
  File "/Users/myuser/.local/share/virtualenvs/ansible-6KFbR7gx/bin/molecule", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/Users/myuser/.local/share/virtualenvs/ansible-6KFbR7gx/lib/python3.11/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/myuser/.local/share/virtualenvs/ansible-6KFbR7gx/lib/python3.11/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/Users/myuser/.local/share/virtualenvs/ansible-6KFbR7gx/lib/python3.11/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/myuser/.local/share/virtualenvs/ansible-6KFbR7gx/lib/python3.11/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/myuser/.local/share/virtualenvs/ansible-6KFbR7gx/lib/python3.11/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/myuser/.local/share/virtualenvs/ansible-6KFbR7gx/lib/python3.11/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/myuser/.local/share/virtualenvs/ansible-6KFbR7gx/lib/python3.11/site-packages/click/decorators.py", line 33, in new_func
    return f(get_current_context(), *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/myuser/.local/share/virtualenvs/ansible-6KFbR7gx/lib/python3.11/site-packages/molecule/command/init/scenario.py", line 164, in scenario
    s.execute()
  File "/Users/myuser/.local/share/virtualenvs/ansible-6KFbR7gx/lib/python3.11/site-packages/molecule/command/init/scenario.py", line 99, in execute
    util.run_command(cmd, env=env, check=True)
  File "/Users/myuser/.local/share/virtualenvs/ansible-6KFbR7gx/lib/python3.11/site-packages/molecule/util.py", line 146, in run_command
    raise CalledProcessError(
subprocess.CalledProcessError: Command '['ansible-playbook', '-i', 'localhost,', '--connection=local', '--extra-vars', '{"dependency_name": "galaxy", "driver_name": "default", "provisioner_name": "ansible", "scenario_name": "default", "subcommand": "molecule.command.init.scenario"}', '/Users/myuser/.local/share/virtualenvs/ansible-6KFbR7gx/lib/python3.11/site-packages/molecule/data/init-scenario.yml']' returned non-zero exit status 127.

Running the mentioned ansible-playbook command manually is working fine. As soon as I downgrade molecule to version 5.1.0 it's also working fine. So it seems that the problem was introduced with version 6.0.0. Looks like the virtual env is completely ignored, when other commands are called.

Reproducing example

No response

[priyamsahoo]

Neither pipenv nor fish is supported by us.
But, we will accept a pull request if you have a fix for it!

[mathias-ioki]

I've also tested:

• using virtual-env (which is the recommended installation method)
• using zsh (on a Mac)

None of them worked. Exactly the same setup is working with molecule 5.1.0. So I would expect, that something broke on the way to 6.0.