vitabaks/autobase

ansible error in docker

Closed this issue · 2 comments

When I committed to create new cluster command from GUI It gave me an error ( 3 nodes cluster on my private environment)
autobase running on docker, and no network accessible issue

TASK [Gathering Facts] *********************************************************
fatal: [192.168.1.50]: FAILED! => {"ansible_facts": {}, "changed": false, "failed_modules": {"ansible.legacy.setup": {"failed": true, "module_stderr": "Warning: Permanently added '192.168.1.50' (ED25519) to the list of known hosts.\r\n/usr/bin/env: ‘python3’: No such file or directory\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 127}}, "msg": "The following modules failed to execute: ansible.legacy.setup\n"}
fatal: [192.168.1.51]: FAILED! => {"ansible_facts": {}, "changed": false, "failed_modules": {"ansible.legacy.setup": {"failed": true, "module_stderr": "Warning: Permanently added '192.168.1.51' (ED25519) to the list of known hosts.\r\n/usr/bin/env: ‘python3’: No such file or directory\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 127}}, "msg": "The following modules failed to execute: ansible.legacy.setup\n"}
fatal: [192.168.1.52]: FAILED! => {"ansible_facts": {}, "changed": false, "failed_modules": {"ansible.legacy.setup": {"failed": true, "module_stderr": "Warning: Permanently added '192.168.1.52' (ED25519) to the list of known hosts.\r\n/usr/bin/env: ‘python3’: No such file or directory\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 127}}, "msg": "The following modules failed to execute: ansible.legacy.setup\n"}
![image_2024-12-19_201649865](https://github.com/user-attachments/assets/84cba4bb-5e8d-44a0-8279-6cd81bc4dd5d)

Make sure that the target servers have python3, try execute the command /usr/bin/env python3

Oh I see It's my mistake

thanks