Comment 22 for bug 1596620

Reviewed: https://review.openstack.org/340013
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-repo_build/commit/?id=fa0d6d003e40195000646846f5a429a45e29e8e6
Submitter: Jenkins
Branch: stable/mitaka

commit fa0d6d003e40195000646846f5a429a45e29e8e6
Author: Jesse Pretorius <email address hidden>
Date: Wed May 4 10:48:09 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

    Change-Id: Ibaf881cb3d524f5f886377a48bd7748d4a7cdd90
    (cherry picked from commit 13e70a7329d0795657f8e4fdb8a614562d0b3dee)