Not sure when this happened, but I've noticed it via @renovatebot PRs - although I don't think responsible.
The full error
ERROR! the role 'mirsg.infrastructure.install_python' was not found in /home/runner/work/ansible-collection-infra/ansible-collection-infra/ansible_collections/mirsg/infrastructure/playbooks/molecule/resources/monitoring/roles:/home/runner/.cache/molecule/playbooks/centos7_monitoring/roles:/home/runner/work/ansible-collection-infra/ansible-collection-infra/ansible_collections/mirsg/infrastructure:/home/runner/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/home/runner/work/ansible-collection-infra/ansible-collection-infra/ansible_collections/mirsg/infrastructure/playbooks/molecule/resources/monitoring
The error appears to be in '/home/runner/work/ansible-collection-infra/ansible-collection-infra/ansible_collections/mirsg/infrastructure/playbooks/molecule/resources/monitoring/converge.yml': line 7, column 7, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
roles:
- role: mirsg.infrastructure.install_python
^ here
CRITICAL Ansible return code was 1, command was: ansible-playbook --inventory /home/runner/.cache/molecule/playbooks/centos7_monitoring/inventory --skip-tags molecule-notest,notest --syntax-check /home/runner/work/ansible-collection-infra/ansible-collection-infra/ansible_collections/mirsg/infrastructure/playbooks/molecule/resources/monitoring/converge.yml
Short Description
Not sure when this happened, but I've noticed it via @renovatebot PRs - although I don't think responsible.
The full error
Evidence/Steps to Reproduce
No response
Acceptance Criteria/Expected Behaviour
No response
Details
No response
Resolution
No response