Currently all pip install tasks only require the package to be
present. This means that when an environment undergoes a minor
upgrade the package is not upgraded to the same version that
was tested with. This ultimately results in a deployed
environment that does not match the tested environment.
While for the services installed into venvs this is not an
issue, it does affect those which do not use venvs and any
packages which are installed outside of a venv or on top
of a venv.
This patch changes the behaviour to ensure that the install
task will always use the latest available package. In
developer_mode this will mean using the version specified
in upper-constraints, and in an integrated build this will
mean the version which is available in the wheel repo's
folder for the tag.
Reviewed: https:/ /review. openstack. org/343629 /git.openstack. org/cgit/ openstack/ openstack- ansible/ commit/ ?id=413151fddc0 701c1659ba691ec dccf4eec57c724
Committed: https:/
Submitter: Jenkins
Branch: master
commit 413151fddc0701c 1659ba691ecdccf 4eec57c724
Author: Jesse Pretorius <email address hidden>
Date: Mon Jul 18 14:06:20 2016 +0100
Change pip install task state to 'latest'
Currently all pip install tasks only require the package to be
present. This means that when an environment undergoes a minor
upgrade the package is not upgraded to the same version that
was tested with. This ultimately results in a deployed
environment that does not match the tested environment.
While for the services installed into venvs this is not an
issue, it does affect those which do not use venvs and any
packages which are installed outside of a venv or on top
of a venv.
This patch changes the behaviour to ensure that the install
task will always use the latest available package. In
developer_mode this will mean using the version specified
in upper-constraints, and in an integrated build this will
mean the version which is available in the wheel repo's
folder for the tag.
Related-Bug: 1596620 461505f64dfd725 6baff995653
Change-Id: I6b6464d517497e