Comment 30 for bug 1596620

Reviewed: https://review.openstack.org/340008
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_neutron/commit/?id=ed228adc369832efa4a55e047ce8bf6fef497cf1
Submitter: Jenkins
Branch: stable/mitaka

commit ed228adc369832efa4a55e047ce8bf6fef497cf1
Author: Jesse Pretorius <email address hidden>
Date: Wed May 4 10:38:50 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: I22821cb24642aad4bface0ae0838351cd0cce257
    (cherry picked from commit 5ce4d64150e2636da06d3fb61a20b20ced971cef)