Closed trfore closed 1 year ago
Molecule test fail to version lock MongoDB in CentOS 8, this is related to community.general.yum_versionlock >= 7.2.0 as pinning the collection to 7.1.0 resolves the issue.
community.general.yum_versionlock >= 7.2.0
7.1.0
ansible-galaxy collection install community.general:7.1.0
Note: This issue does not occur when locking MongoDB to version 5.0.20.
5.0.20
MOLECULE_MONGODB_VERSION="5.0.20" MOLECULE_IMAGE="trfore/docker-centos8-systemd" molecule test -s default
Steps to reproduce the behavior:
MOLECULE_MONGODB_VERSION="4.4.23" MOLECULE_IMAGE="trfore/docker-centos8-systemd" molecule test -s default
OR
MOLECULE_MONGODB_VERSION="6.0.9" MOLECULE_IMAGE="trfore/docker-centos8-systemd" molecule test -s default
TASK [ansible-role-mongodb-install : Hold MongoDB packages] ******************** fatal: [instance]: FAILED! => {"changed": false, "msg": "Adding versionlock on: mongodb-org-0:*..."}
Task OK and packages locked
ansible --version
ansible [core 2.15.2] config file = None configured module search path = ['/home/trf/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /home/trf/miniconda3/envs/ansible-py3.11/lib/python3.11/site-packages/ansible ansible collection location = /home/trf/.ansible/collections:/usr/share/ansible/collections executable location = /home/trf/miniconda3/envs/ansible-py3.11/bin/ansible python version = 3.11.4 (main, Jul 5 2023, 13:45:01) [GCC 11.2.0] (/home/trf/miniconda3/envs/ansible-py3.11/bin/python) jinja version = 3.1.2 libyaml = True molecule 6.0.1 using python 3.11 ansible:2.15.2 azure:23.4.1 from molecule_plugins containers:23.4.1 from molecule_plugins requiring collections: ansible.posix>=1.3.0 community.docker>=1.9.1 containers.podman>=1.8.1 default:6.0.1 from molecule docker:23.4.1 from molecule_plugins requiring collections: community.docker>=3.0.2 ansible.posix>=1.4.0 ec2:23.4.1 from molecule_plugins gce:23.4.1 from molecule_plugins requiring collections: google.cloud>=1.0.2 community.crypto>=1.8.0 podman:23.4.1 from molecule_plugins requiring collections: containers.podman>=1.7.0 ansible.posix>=1.3.0 vagrant:23.4.1 from molecule_plugins Python 3.11.4
cat /etc/os-release
Relevant GH runner logs:
Recent commit to community.general.yum_versionlock in community.general version 7.2.0:
community.general.yum_versionlock
7.2.0
Describe the bug
Molecule test fail to version lock MongoDB in CentOS 8, this is related to
community.general.yum_versionlock >= 7.2.0
as pinning the collection to7.1.0
resolves the issue.Note: This issue does not occur when locking MongoDB to version
5.0.20
.To Reproduce
Steps to reproduce the behavior:
OR
Expected behavior
Task OK and packages locked
Your environment
ansible --version
):cat /etc/os-release
): GH runner Ubuntu-Latest and Local