FS#76832 - [ansible-lint] No such file or directory: '/usr/lib/python3.10/site-packages/ansiblelint/data/profil

Attached to Project: Community Packages
Opened by Simon Tunnat (imon) - Thursday, 15 December 2022, 09:26 GMT
Last edited by Toolybird (Toolybird) - Thursday, 15 December 2022, 20:14 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To freswa (frederik)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Ansible Lint 6.10.0-1 fails with the following error message:


$ ansible-lint --version

Traceback (most recent call last):
File "/usr/bin/ansible-lint", line 5, in <module>
from ansiblelint.__main__ import _run_cli_entrypoint
File "/usr/lib/python3.10/site-packages/ansiblelint/__main__.py", line 40, in <module>
from ansiblelint import cli
File "/usr/lib/python3.10/site-packages/ansiblelint/cli.py", line 12, in <module>
from ansiblelint.config import DEFAULT_KINDS, DEFAULT_WARN_LIST, PROFILES
File "/usr/lib/python3.10/site-packages/ansiblelint/config.py", line 100, in <module>
PROFILES = yaml_from_file(Path(__file__).parent / "data" / "profiles.yml")
File "/usr/lib/python3.10/site-packages/ansiblelint/loaders.py", line 23, in yaml_from_file
with open(str(filepath), encoding="utf-8") as content:
FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3.10/site-packages/ansiblelint/data/profiles.yml'


When I downgrade to Ansible Lint 6.9.1-2 it works fine again:


$ ansible-lint --version

ansible-lint 6.9.1 using ansible 2.14.1
A new release of ansible-lint is available: 6.9.1 → 6.10.0
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 15 December 2022, 20:14 GMT
Reason for closing:  Fixed
Additional comments about closing:  ansible-lint 6.10.0-2
Comment by freswa (frederik) - Thursday, 15 December 2022, 12:31 GMT
6.10.0-2 fixes the issue.
Reported upstream: https://github.com/ansible/ansible-lint/issues/2826
Comment by Simon Tunnat (imon) - Thursday, 15 December 2022, 14:32 GMT
I can confirm the fix :)

Loading...