Bug 2213747

Summary: [abrt] python3-ansible-lint: get_cache_dir(): prerun.py:13:get_cache_dir:AttributeError: 'str' object has no attribute 'resolve'
Product: [Fedora] Fedora Reporter: Julien Tognazzi <julien.tognazzi>
Component: python-ansible-compatAssignee: chedi toueiti <chedi.toueiti>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 37CC: chedi.toueiti, djuran, kevin, maxwell, pnemade, rosendeh, winter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3015160b8b8a6b09813ae4820625aae572c3b95f
Whiteboard: abrt_hash:c5641727f0be9df4880e0686f8310f3b3f4c5a71;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-01-15 12:17:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cpuinfo
none
File: environ
none
File: mountinfo
none
File: namespaces
none
File: open_fds none

Description Julien Tognazzi 2023-06-09 06:56:50 UTC
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'

Comment 1 Julien Tognazzi 2023-06-09 06:56:53 UTC
Created attachment 1969872 [details]
File: backtrace

Comment 2 Julien Tognazzi 2023-06-09 06:56:54 UTC
Created attachment 1969873 [details]
File: cpuinfo

Comment 3 Julien Tognazzi 2023-06-09 06:56:55 UTC
Created attachment 1969874 [details]
File: environ

Comment 4 Julien Tognazzi 2023-06-09 06:56:56 UTC
Created attachment 1969875 [details]
File: mountinfo

Comment 5 Julien Tognazzi 2023-06-09 06:56:58 UTC
Created attachment 1969876 [details]
File: namespaces

Comment 6 Julien Tognazzi 2023-06-09 06:56:59 UTC
Created attachment 1969877 [details]
File: open_fds

Comment 7 Parag Nemade 2023-06-10 13:40:34 UTC
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.

Comment 8 Parag Nemade 2023-08-03 06:54:24 UTC
*** Bug 2214535 has been marked as a duplicate of this bug. ***

Comment 9 Parag Nemade 2023-08-03 06:55:08 UTC
*** Bug 2213600 has been marked as a duplicate of this bug. ***

Comment 10 Parag Nemade 2023-08-03 06:55:11 UTC
*** Bug 2213826 has been marked as a duplicate of this bug. ***

Comment 11 Parag Nemade 2023-08-03 06:57:31 UTC
*** Bug 2183173 has been marked as a duplicate of this bug. ***

Comment 12 Parag Nemade 2023-08-11 15:55:59 UTC
*** Bug 2231376 has been marked as a duplicate of this bug. ***

Comment 13 Parag Nemade 2023-09-18 06:15:46 UTC
*** Bug 2238022 has been marked as a duplicate of this bug. ***

Comment 14 Aoife Moloney 2023-11-23 01:46:24 UTC
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.

Comment 15 Aoife Moloney 2024-01-15 12:17:23 UTC
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.