Disable galaxy dependancy manager not being respected?

[smirgel]

Hi,

I'm trying to disable the galaxy dependancy manager without any luck (it is being invoked even though enabled is set to false).

Ansible version:

ansible [core 2.12.0]
  config file = None
  configured module search path = ['/home/myuser/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.8/site-packages/ansible
  ansible collection location = /home/myuser/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/local/bin/ansible
  python version = 3.8.8 (default, Aug 11 2021, 06:52:42) [GCC 8.5.0 20210514 (Red Hat 8.5.0-3)]
  jinja version = 3.1.2
  libyaml = True

Molecule version:

molecule 3.6.1 using python 3.8 
    ansible:2.12.0
    delegated:3.6.1 from molecule

Config used to disable galaxy dependancy manager:

---
dependency:
  name: galaxy
  enabled: False

What is strange is that if I try to switch to shell dependancy manager galaxy is still invoked. It is as if the config is being overriden from somewhere? I know the config is being read because if I change the dependancy name to some nonsense I get an error.

Any ideas?

[Shaps]

I think, depending on the driver you are using, there is a set of 'fixed' requirements. For example the docker driver needs the community.docker collection, which should be installed automatically, and that should be what uses ansible-galaxy. It could also be the pre-run that does it - https://molecule.readthedocs.io/en/latest/configuration.html#prerun

[zhan9san]

Hi @smirgel

This issue can be reproduced.

The version is not compatible with semantic versioning.

The root cause is as below, source code

#version: 1.0.0
version: this_is_not_a_semantic_version

Must be compatible with semantic versioning.

You can get the version description from collections_galaxy_meta

[smirgel]

Yeah I know but why is it being installed at all? I am explicitly setting the "enabled: False" setting. I can fix the version but "ansible-galaxy collection install" is still being called which is what I am trying to disable.

[zhan9san]

molecule tried to find galaxy.yml in work dir, and then ../../galaxy.yml.

See, ansible_compat

1. If either of them exists, the repo is treated as a collection.
2. If both are not found, the repo is treated as a standalone role.

Your repo is treated as a collection as ../../galaxy.yml exists.

Then molecule would install the collection(your repo) instead of dependency by ansible-galaxy.

[apatard]

Directory layout:

$ tree .
.
├── depcol
│   ├── galaxy.yml
│   └── roles
│       └── myrole
│           ├── molecule
│           │   └── get_file_raw
│           │       ├── converge.yml
│           │       └── molecule.yml
│           └── tasks
└── README.md

6 directories, 4 files

Available in this repo: https://github.com/smirgel/deptest2

PWD is depcol/roles/myrole when running:

$ molecule test -s get_file_raw
INFO     get_file_raw scenario test matrix: lint, converge, verify
INFO     Performing prerun...
INFO     Set ANSIBLE_LIBRARY=/root/.cache/ansible-compat/a8f7d1/modules:/root/.ansible/plugins/modules:/usr/share/ansible/plugins/modules
INFO     Set ANSIBLE_COLLECTIONS_PATH=/root/.cache/ansible-compat/a8f7d1/collections:/root/.ansible/collections:/usr/share/ansible/collections
INFO     Set ANSIBLE_ROLES_PATH=/root/.cache/ansible-compat/a8f7d1/roles:/root/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles
INFO     Running ansible-galaxy collection install -v --force -p /root/.cache/ansible-compat/a8f7d1/collections ../..
WARNING  Retrying execution failure 250 of: ansible-galaxy collection install -v --force -p /root/.cache/ansible-compat/a8f7d1/collections ../..
ERROR    Command returned 250 code:

That's prerun from ansible-compat. If you don't want it, just add "prerun: false" in your molecule.yml file

[smirgel]

Thanks @apatard and @zhan9san ! I'll have to investigate what else is disabled when I disable prerun.