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
affects_2.15bugThis issue/PR relates to a bug.has_prThis issue has an associated PR.moduleThis issue/PR relates to a module.P3Priority 3 - Approved, No Time LimitationverifiedThis issue has been verified/reproduced by maintainer
When installing the latest version of a git repository using ansible.builtin.pip, the status is never set to changed, not even when using state:forcereinstall. If I investigate the virtual environment on the provisioned system using pip freeze, I see that the virtual environment was in fact reinstalled, using the latest changes from git. However, since changed is never set to true, none of the defined notify handlers are triggered.
If these files are incorrect, please update the component name section of the description or use the component bot command.
mattclay
added
P3
Priority 3 - Approved, No Time Limitation
and removed
needs_triage
Needs a first human triage before being processed.
labels
Sep 21, 2023
The problem here is that we compare the state before and after installing using pip list --format=freeze and that output only contains <package>==<version> and the version in both of your branches is the same.
We can fix this, I think by using pip freeze instead of pip list --format=freeze as pip freeze would display something like:
affects_2.15bugThis issue/PR relates to a bug.has_prThis issue has an associated PR.moduleThis issue/PR relates to a module.P3Priority 3 - Approved, No Time LimitationverifiedThis issue has been verified/reproduced by maintainer
Summary
When installing the latest version of a git repository using
ansible.builtin.pip
, the status is never set to changed, not even when usingstate:forcereinstall
. If I investigate the virtual environment on the provisioned system usingpip freeze
, I see that the virtual environment was in fact reinstalled, using the latest changes from git. However, sincechanged
is never set to true, none of the definednotify
handlers are triggered.Issue Type
Bug Report
Component Name
pip
Ansible Version
Configuration
OS / Environment
Ubuntu 22.04.3 LTS
Steps to Reproduce
Expected Results
I expect ansible to set the task to
changed
if pip installs a newer version from a git repository.Actual Results
Code of Conduct
The text was updated successfully, but these errors were encountered: