Timeline for How to solve Ansible venv runtime exception in specific versions?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 9 at 8:17 | vote | accept | Turtle10000 | ||
| Jul 2 at 15:11 | answer | added | Turtle10000 | timeline score: 0 | |
| Jul 2 at 14:15 | comment | added | Turtle10000 | I did and it does not work. It's likely a compatibility issue between python3.12 and older Ansible versions. Using Ansible 2.9 instead of 5.1 leads to this: github.com/ansible/ansible/issues/81946 | |
| Jun 27 at 23:50 | comment | added | Vladimir Botka | Create venv as described in the above link. Then, install Ansible. | |
| Jun 27 at 23:48 | comment | added | Turtle10000 | I can create a venv with running Ansible, just not in the constellation as described above. | |
| Jun 27 at 18:05 | comment | added | Vladimir Botka | See redhat.com/sysadmin/python-venv-ansible | |
| Jun 27 at 17:57 | history | asked | Turtle10000 | CC BY-SA 4.0 |