Description of problem: Accidentally attempted to execute `ansible -i non_existent/directory/` Version-Release number of selected component: ansible-2.9.27-1.fc34 Additional info: reporter: libreport-2.15.2 cmdline: /usr/bin/python3 /usr/bin/ansible db -i ../ansible-inventory/ivanovo/ --list-hosts crash_function: unfrackpath exception_type: FileNotFoundError executable: /usr/bin/ansible interpreter: python3-3.9.7-1.fc34.x86_64 kernel: 5.14.15-200.fc34.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: path.py:55:unfrackpath:FileNotFoundError: [Errno 2] No such file or directory Traceback (most recent call last): File "/usr/bin/ansible", line 62, in <module> import ansible.constants as C File "/usr/lib/python3.9/site-packages/ansible/constants.py", line 175, in <module> config = ConfigManager() File "/usr/lib/python3.9/site-packages/ansible/config/manager.py", line 283, in __init__ self._config_file = find_ini_config_file(self.WARNINGS) File "/usr/lib/python3.9/site-packages/ansible/config/manager.py", line 240, in find_ini_config_file potential_paths.append(unfrackpath("~/.ansible.cfg", follow=False)) File "/usr/lib/python3.9/site-packages/ansible/utils/path.py", line 55, in unfrackpath b_basedir = to_bytes(os.getcwd(), errors='surrogate_or_strict') FileNotFoundError: [Errno 2] No such file or directory Local variables in innermost frame: path: '~/.ansible.cfg' follow: False basedir: None b_basedir: None
Created attachment 1844105 [details] File: backtrace
Created attachment 1844106 [details] File: cgroup
Created attachment 1844107 [details] File: cpuinfo
Created attachment 1844108 [details] File: environ
Created attachment 1844109 [details] File: mountinfo
Created attachment 1844110 [details] File: namespaces
Created attachment 1844111 [details] File: open_fds
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 '34'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.