-
-
Notifications
You must be signed in to change notification settings - Fork 606
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ansible-core:2.17
/ Ansible 10 not supported
#1525
Comments
Here's a great post about the issue: https://www.jeffgeerling.com/blog/2024/newer-versions-ansible-dont-work-rhel-8 @codepuncher I assume your server is running Ubuntu 18 or older? |
I'm inclined to leave Trellis on |
Hi @swalkinshaw, This is happening on Ubuntu 22.04.4 (GitHub-hosted runner) as well as my WSL instance which is also Ubuntu 22.04.4 On the remote server (Kinsta), there is: /usr/bin/python -> /usr/bin/python2.7
/usr/bin/python2 -> python2.7
/usr/bin/python2.7
/usr/bin/python3 -> python3.8
/usr/bin/python3.8 On my WSL (which would be similar on the GitHub runner): /usr/bin/python3 -> python3.10*
/usr/bin/python3-config -> python3.10-config*
/usr/bin/python3.10*
/usr/bin/python3.10-config -> x86_64-linux-gnu-python3.10-config* I can see through the Shouldn't it be using Python 3.10 from the virtualenv, though? More debug info: # roles/deploy/tasks/update.yml
- name: Get python path
command: which python
no_log: false
register: pp_1
- ansible.builtin.debug:
var: pp_1
verbosity: 4
- name: Get python version
command: python --version
no_log: false
register: pv_1
- ansible.builtin.debug:
var: pv_1
verbosity: 4
- name: Get python path
command: which python
no_log: false
connection: local
register: pp_2
- ansible.builtin.debug:
var: pp_2
verbosity: 4
- name: Get python version
command: python --version
no_log: false
connection: local
register: pv_2
- ansible.builtin.debug:
var: pv_2
verbosity: 4
- name: Clone project files
git:
repo: "{{ project_git_repo }}"
dest: "{{ project_source_path }}"
version: "{{ project_version }}"
accept_hostkey: "{{ project.repo_accept_hostkey | default(repo_accept_hostkey | default(true)) }}"
force: yes
ignore_errors: true
no_log: false
register: git_clone
|
In your original error the failure was on task "Clone project files" which is not a local connection; meaning it's being executed on the remote server by Python on that server, not your local machine. This means it's using the system version of Python 3 on Ubuntu 22.04 and, unfortunately, completely separate and unrelated from your local virtualenv setup that the CLI manages. I assume this must be related to Ansible's changes of how it detects the Python interpreter, but I guess not the same issue as it not supporting <3.8 now. @codepuncher can you try setting your |
Hi @swalkinshaw, thanks for that; I have added I'll close my accompanying PR with this as an alternative. |
Version
80a491e
What did you expect to happen?
To be able to run
trellis deploy production
without errorWhat actually happens?
The deploy fails
Steps to reproduce
Ensure that
trellis init && trellis exec ansible --version
showsansible 2.17.x
System info
Error found in GitHub action runner.
Linux, using
roots/setup-trellis-cli
Log output
Please confirm this isn't a support request.
Yes
Other notes
https://docs.ansible.com/ansible/latest/roadmap/COLLECTIONS_10.html
https://docs.ansible.com/ansible/latest/roadmap/ROADMAP_2_17.html#id6
The text was updated successfully, but these errors were encountered: