Comment 6 for bug 1658948

Reviewed: https://review.openstack.org/424416
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=3859663a6bb4b15705185b6b233e4b66e5728a89
Submitter: Jenkins
Branch: stable/newton

commit 3859663a6bb4b15705185b6b233e4b66e5728a89
Author: Matthew Thode <email address hidden>
Date: Mon Jan 23 12:33:49 2017 -0600

    Apply global-pins as constraints to ensure complete pinning

    The current pinning method for pip/setuptools/wheel works for the
    initial setup of a host or python venv. However, when a python
    package which has one of these in its requirements is installed
    onto the host or into the venv and the '--upgrade' option is given
    to pip, the package will be upgraded to the latest version available
    within the given constraints.

    As OpenStack's requirements management process does not cater for
    the pip, setuptools or wheel packages we need to ensure that all
    python install tasks prior to the repo being built use our global
    pins as a constraint in addition to the OpenStack uppser constraints.

    As pip's --constraints option can only take a file as an argument
    we have to copy the global pins file to the target which will use
    it. This file can be removed from the host once the repo is built.

    Combined backport of:
    - https://review.openstack.org/424283
    - https://review.openstack.org/424540

    Closes-Bug: #1658773
    Closes-Bug: #1658948
    Change-Id: Iccbb2e4a126a1cc7a4c94ab41b7ce8ef54d89990
    (cherry picked from commit 253ea10d266f5ce4a11249ed3c2f1fe3568a8ace)