Description of problem: It happened with the Visual Code ansible extension Version-Release number of selected component: python3-ansible-lint-1:6.10.0-1.fc37 Additional info: reporter: libreport-2.17.10 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-code-139854.scope cmdline: /usr/bin/python3 -sP /bin/ansible-lint --offline --nocolor -f codeclimate /home/tognjul1/Documents/els/osdeploy/ansible/playbooks/tc_create_branch_config.yml crash_function: get_cache_dir exception_type: AttributeError executable: /bin/ansible-lint interpreter: python3-3.11.3-2.fc37.x86_64 kernel: 6.3.5-100.fc37.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: prerun.py:13:get_cache_dir:AttributeError: 'str' object has no attribute 'resolve' Traceback (most recent call last): File "/bin/ansible-lint", line 8, in <module> sys.exit(_run_cli_entrypoint()) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/site-packages/ansiblelint/__main__.py", line 344, in _run_cli_entrypoint sys.exit(main(sys.argv)) ^^^^^^^^^^^^^^ File "/usr/lib/python3.11/site-packages/ansiblelint/__main__.py", line 197, in main initialize_options(argv[1:]) File "/usr/lib/python3.11/site-packages/ansiblelint/__main__.py", line 110, in initialize_options options.cache_dir = get_cache_dir(options.project_dir) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/site-packages/ansible_compat/prerun.py", line 13, in get_cache_dir basename = project_dir.resolve().name.encode(encoding="utf-8") ^^^^^^^^^^^^^^^^^^^ AttributeError: 'str' object has no attribute 'resolve' Local variables in innermost frame: project_dir: '/home/tognjul1/Documents/els/osdeploy'
Created attachment 1969872 [details] File: backtrace
Created attachment 1969873 [details] File: cpuinfo
Created attachment 1969874 [details] File: environ
Created attachment 1969875 [details] File: mountinfo
Created attachment 1969876 [details] File: namespaces
Created attachment 1969877 [details] File: open_fds
This happened due to new update of ansible-compat in F37 The last known ansible-lint build is ansible-lint-6.10.0-1.fc37 which is working fine with python-ansible-compat-2.2.7-9.fc37 but then python-ansible-compat directly got an update to 4.0.4-1.fc37 which broke ansible-lint command.
*** Bug 2214535 has been marked as a duplicate of this bug. ***
*** Bug 2213600 has been marked as a duplicate of this bug. ***
*** Bug 2213826 has been marked as a duplicate of this bug. ***
*** Bug 2183173 has been marked as a duplicate of this bug. ***
*** Bug 2231376 has been marked as a duplicate of this bug. ***
*** Bug 2238022 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.