You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like there are no checks that an interpreter already exists prior to attempting to do a pyenv install for it.
I expected that it would be relatively idempotent and if versions were already installed it would not attempt to install them again (or at least not error out if it did), but I don't see any attempt at checking them after looking through the code. However, I see there are idempotence tests, so I'm really confused how this is happening.
I'm using Ansible 6.4.0-1ppa~jammy on Ubuntu 22.04. This commit sums up what my ansible-pyenv configuration looks like in my playbook.
The text was updated successfully, but these errors were encountered:
Opened a draft MR that fixes this issue for me. It has some other work that probably should be added before merging but it at least gives (I hope) a good starting point. I don't know enough about how tests work in Travis with Ansible to write a test case that triggers this failure, but that's one thing that probably should be added to that MR.
Maybe I'm using this wrong, but on Linux when I re-run a playbook using this role, after a previous success, it fails:
It looks like there are no checks that an interpreter already exists prior to attempting to do a pyenv install for it.
I expected that it would be relatively idempotent and if versions were already installed it would not attempt to install them again (or at least not error out if it did), but I don't see any attempt at checking them after looking through the code. However, I see there are idempotence tests, so I'm really confused how this is happening.
I'm using Ansible
6.4.0-1ppa~jammy
on Ubuntu 22.04. This commit sums up what my ansible-pyenv configuration looks like in my playbook.The text was updated successfully, but these errors were encountered: