From be11ed00df30cde3b6b657d35f337c97948d2d3b Mon Sep 17 00:00:00 2001 From: Jesse Pretorius Date: Wed, 4 May 2016 10:43:41 +0100 Subject: [PATCH] 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 Change-Id: Id04b2f74831e3422b036308c638be5428509e57a (cherry picked from commit cf882feb534c74f3d53d854cd135d36f3abfe8be) --- tasks/swift_install.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tasks/swift_install.yml b/tasks/swift_install.yml index a347a203..df3d412c 100644 --- a/tasks/swift_install.yml +++ b/tasks/swift_install.yml @@ -90,7 +90,7 @@ - name: Install requires pip packages pip: name: "{{ item }}" - state: present + state: latest extra_args: "{{ pip_install_options_fact }}" register: install_packages until: install_packages|success @@ -209,7 +209,7 @@ - name: Install pip packages (venv) pip: name: "{{ item }}" - state: present + state: latest virtualenv: "{{ swift_venv_bin | dirname }}" virtualenv_site_packages: "no" extra_args: "{{ pip_install_options_fact }}" @@ -233,7 +233,7 @@ - name: Install pip packages (no venv) pip: name: "{{ item }}" - state: present + state: latest extra_args: "{{ pip_install_options_fact }}" register: install_packages until: install_packages|success