Add Debian 7 backend #3
Conversation
|
Instead of introducing
This way we won't be exposing any details about the network interface. |
There was a problem hiding this comment.
The changes don't work on my side. I first had SSH connection issues that were solved in the comment below. Then I had this error:
fatal: [debian1]: FAILED! => {"ansible_facts": {}, "changed": false, "failed_modules": {"ansible.legacy.setup": {"ansible_facts": {"discovered_interpreter_python": "/usr/bin/python3"}, "failed": true, "module_stderr": "Shared connection to 127.0.0.1 closed.\r\n", "module_stdout": "/bin/sh: 1: /usr/bin/python3: not found\r\n", "msg": "The module failed to execute correctly, you probably need to set the interpreter.\nSee stdout/stderr for the exact error", "rc": 127, "warnings": ["No python interpreters found for host debian1 (tried ['python3.12', 'python3.11', 'python3.10', 'python3.9', 'python3.8', 'python3.7', '/usr/bin/python3', 'python3'])"]}}, "msg": "The following modules failed to execute: ansible.legacy.setup\n"}
Okay, so I added ansible_python_interpreter=/usr/bin/python to the inventory.ini file, but now I see a much bigger problem when I try to run ansible-playbook for CVEX/ansible/linux_router.yml:
fatal: [debian1]: FAILED! => {"ansible_facts": {}, "changed": false, "failed_modules": {"ansible.legacy.setup": {"exception": "Traceback (most recent call last):\r\n File "/home/vagrant/.ansible/tmp/ansible-tmp-1732197050.687829-265310-66440703984384/AnsiballZ_setup.py", line 107, in \r\n _ansiballz_main()\r\n File "/home/vagrant/.ansible/tmp/ansible-tmp-1732197050.687829-265310-66440703984384/AnsiballZ_setup.py", line 99, in _ansiballz_main\r\n invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\r\n File "/home/vagrant/.ansible/tmp/ansible-tmp-1732197050.687829-265310-66440703984384/AnsiballZ_setup.py", line 44, in invoke_module\r\n from ansible.module_utils import basic\r\n File "/tmp/ansible_ansible.legacy.setup_payload_x_lYCY/ansible_ansible.legacy.setup_payload.zip/ansible/module_utils/basic.py", line 17\r\n msg=f"ansible-core requires a minimum of Python version {'.'.join(map(str, _PY_MIN))}. Current version: {''.join(sys.version.splitlines())}",\r\n ^\r\nSyntaxError: invalid syntax\r\n", "failed": true, "module_stderr": "Shared connection to 127.0.0.1 closed.\r\n", "module_stdout": "Traceback (most recent call last):\r\n File "/home/vagrant/.ansible/tmp/ansible-tmp-1732197050.687829-265310-66440703984384/AnsiballZ_setup.py", line 107, in \r\n _ansiballz_main()\r\n File "/home/vagrant/.ansible/tmp/ansible-tmp-1732197050.687829-265310-66440703984384/AnsiballZ_setup.py", line 99, in _ansiballz_main\r\n invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\r\n File "/home/vagrant/.ansible/tmp/ansible-tmp-1732197050.687829-265310-66440703984384/AnsiballZ_setup.py", line 44, in invoke_module\r\n from ansible.module_utils import basic\r\n File "/tmp/ansible_ansible.legacy.setup_payload_x_lYCY/ansible_ansible.legacy.setup_payload.zip/ansible/module_utils/basic.py", line 17\r\n msg=f"ansible-core requires a minimum of Python version {'.'.join(map(str, _PY_MIN))}. Current version: {''.join(sys.version.splitlines())}",\r\n ^\r\nSyntaxError: invalid syntax\r\n", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}}, "msg": "The following modules failed to execute: ansible.legacy.setup\n"}
Does it actually work on your side? What's the trick?
| @@ -56,7 +56,7 @@ def get_ansible_inventory(self) -> Path: | |||
| f"ansible_port={self.vag.port()} " | |||
| f"ansible_user={self.vag.user()} " | |||
| f"ansible_ssh_private_key_file={self.vag.keyfile()} " | |||
| f"ansible_ssh_common_args='-o StrictHostKeyChecking=no'") | |||
| f"ansible_ssh_common_args='-o StrictHostKeyChecking=no -oHostKeyAlgorithms=+ssh-rsa'") | |||
There was a problem hiding this comment.
It doesn't seem to be enough. I had to add also these parameters to overcome SSH connection issues:
-o PubkeyAcceptedKeyTypes=+ssh-rsa -o UserKnownHostsFile=/dev/null
There was a problem hiding this comment.
What version of ansible are you using?
There was a problem hiding this comment.
$ ansible --version
ansible [core 2.17.1]
$ apt list | grep ansible
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
ansible-core/jammy-updates,jammy-updates 2.12.0-1ubuntu0.1 all
ansible-lint/jammy,jammy 5.4.0-2 all
ansible-mitogen/jammy,jammy 0.3.1-3 all
ansible/jammy,jammy 2.10.7+merged+base+2.10.8+dfsg-1 all
python-ansible-runner-doc/jammy,jammy 2.1.1-1 all
python-networking-ansible-doc/jammy,jammy 17.0.0-2 all
python3-ansible-runner/jammy,jammy 2.1.1-1 all
python3-networking-ansible/jammy,jammy 17.0.0-2 all
There was a problem hiding this comment.
Ok, it appears Ansible 2.17 dropped Python 2.7. So we would need some other process to bootstrap this system. This actually seems like a rather significant limitation for reproducibility - for instance as Ubuntu 22 becomes out of date.
There was a problem hiding this comment.
I see. We may need our own custom version of Debian 7 box with Python3 pre-installed in it. I'll take care of that.
No description provided.