Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[6.0.0a0] Failed to find driver vagrant. #3967

Closed
konstruktoid opened this issue Jul 12, 2023 · 4 comments
Closed

[6.0.0a0] Failed to find driver vagrant. #3967

konstruktoid opened this issue Jul 12, 2023 · 4 comments
Labels

Comments

@konstruktoid
Copy link
Contributor

Issue Type

  • Bug report

Molecule and Ansible details

$ tox -epy311-ansible7
py311-ansible7: install_deps> python -I -m pip install ansible-lint ansible==7 'molecule-plugins[vagrant]' molecule==6.0.0a0

Desired Behavior

Run molecule using the Vagrant driver.

Actual Behaviour

molecule==6.0.0a0

$ tox --recreate -epy311-ansible7
py311-ansible7: remove tox env folder /home/tsj/Code/Git/ansible-role-hardening/.tox/py311-ansible7
py311-ansible7: install_deps> python -I -m pip install ansible-lint ansible==7 'molecule-plugins[vagrant]' molecule==6.0.0a0
py311-ansible7: commands[0]> ansible-lint
WARNING  Skipped installing collection dependencies due to running in offline mode.
[DEPRECATION WARNING]: Encryption using the Python crypt module is deprecated. 
The Python crypt module is deprecated and will be removed from Python 3.13. 
Install the passlib library for continued encryption functionality. This 
feature will be removed in version 2.17. Deprecation warnings can be disabled 
by setting deprecation_warnings=False in ansible.cfg.

Passed: 0 failure(s), 0 warning(s) on 126 files. Profile 'production' was required, but only 'production' profile passed.
py311-ansible7: commands[1]> molecule test
CRITICAL Failed to find driver vagrant. Please ensure that the driver is correctly installed.
py311-ansible7: exit 1 (0.63 seconds) /home/tsj/Code/Git/ansible-role-hardening> molecule test pid=936269
  py311-ansible7: FAIL code 1 (32.86=setup[24.47]+cmd[7.76,0.63] seconds)
  evaluation failed :( (32.90 seconds)
$ tox --recreate -epy311-ansible7
py311-ansible7: remove tox env folder /home/tsj/Code/Git/ansible-role-hardening/.tox/py311-ansible7
py311-ansible7: install_deps> python -I -m pip install ansible-lint ansible==7 molecule 'molecule-plugins[vagrant]'
py311-ansible7: commands[0]> ansible-lint
WARNING  Skipped installing collection dependencies due to running in offline mode.
[DEPRECATION WARNING]: Encryption using the Python crypt module is deprecated. 
The Python crypt module is deprecated and will be removed from Python 3.13. 
Install the passlib library for continued encryption functionality. This 
feature will be removed in version 2.17. Deprecation warnings can be disabled 
by setting deprecation_warnings=False in ansible.cfg.

Passed: 0 failure(s), 0 warning(s) on 126 files. Profile 'production' was required, but only 'production' profile passed.
py311-ansible7: commands[1]> molecule test
WARNING  Driver vagrant does not provide a schema.
INFO     default scenario test matrix: dependency, cleanup, destroy, syntax, create, prepare, converge, idempotence, side_effect, verify, cleanup, destroy
INFO     Performing prerun with role_name_check=0...
INFO     Running ansible-galaxy collection install -v -r requirements.yml
[...]
@konstruktoid
Copy link
Contributor Author

$ python3 -m pip install molecule-plugins[vagrant]@git+https://github.com/ansible-community/molecule-plugins.git git+https://github.com/ansible-community/molecule.git
[...]
Successfully installed molecule-6.0.0a0
$ molecule test
CRITICAL Failed to find driver vagrant. Please ensure that the driver is correctly installed.

@apatard
Copy link
Contributor

apatard commented Jul 21, 2023

you may have been bitten by a "side-effect" of 480c6dc ?
Anyway, maybe you should just close this bug since @ssbarnea (and possibly other guys from RH ?) idea is to kill the drivers: #3919 and looks like there's nothing we can do to change their mind ?

@konstruktoid
Copy link
Contributor Author

Seems like a consequence, yeah :/

I'll let them close the issue with an official response (or whatever to call it) and I've asked a couple of questions regarding v6.

@cidrblock
Copy link
Contributor

Driver support will be reenabled in a future 6 alpha release. Sorry about the bumpy road here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants