L > M upgrade: lxc_hosts fails to install pip packages

[Jimmy McCrory]

Liberty used py_from_git to install lxc-python2, Mitaka+ releases build a wheel for it on the repo servers.

The run-upgrade.sh script includes the --force-reinstall pip option.
https://github.com/openstack/openstack-ansible/blob/stable/mitaka/scripts/run-upgrade.sh#L58

Hosts attempt to reinstall lxc-python2 using the existing pip config locked to a Liberty repo server where the lxc-python2 package does not exist and fail.

TASK: [lxc_hosts | Install pip packages] **************************************
failed: [aio1] => (item=lxc-python2) => {"attempts": 5, "cmd": "/usr/local/bin/pip install --force-reinstall lxc-python2", "failed": true, "item": "lxc-python2"}
msg: Task failed as maximum retries was encountered

FATAL: all hosts have already failed -- aborting

[Jean-Philippe Evrard (jean-philippe-evrard)]

I ran L -> M upgrade without pip_install_options=--force-reinstall works.
Are you suggesting we should remove the pip_install_options?

[Jean-Philippe Evrard (jean-philippe-evrard)]

Following today's bug triage, we have confirmed the issue.
However, a further analysis of the solution have to be done. We need to evaluate the need for a new playbook to remove the pip config file, and the need for adapting the documentation and/or the upgrade shell script.

[Jean-Philippe Evrard (jean-philippe-evrard)]

For context, here is the full conversation about this bug in our bug triage meeting:
http://eavesdrop.openstack.org/irclogs/%23openstack-ansible/%23openstack-ansible.2016-07-05.log.html#t2016-07-05T16:28:14

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/340007

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/340008

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/340009

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/340010

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/340011

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/340012

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/340013

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/340014

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/340015

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/340016

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/340017

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/340018

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/340019

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/340020

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/340018
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-galera_client/commit/?id=4f743109beb5940877a2be6a9bec0656e8af6c74
Submitter: Jenkins
Branch: stable/mitaka

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

    Change-Id: I320a4b8c1876cec12e85985288f084f7396e459b
    (cherry picked from commit 14590f23eae9f826b1a82ae7d3fffb7de8207b13)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/340017
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-lxc_hosts/commit/?id=8eeddc39d7b671d104e02d50b4d933a5ea3f77b1
Submitter: Jenkins
Branch: stable/mitaka

commit 8eeddc39d7b671d104e02d50b4d933a5ea3f77b1
Author: Jesse Pretorius <email address hidden>
Date: Wed May 4 09:43:38 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: I24f9cdf7eb218051b4e75f910ffb5ae280aab976
    (cherry picked from commit 50ded911a5cc50079385216dd13715af1224f631)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/340019
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_tempest/commit/?id=038a436b5c01b58e4da25a6ab5c66bc49447bf79
Submitter: Jenkins
Branch: stable/mitaka

commit 038a436b5c01b58e4da25a6ab5c66bc49447bf79
Author: Jean-Philippe Evrard <email address hidden>
Date: Sat Jul 9 15:26: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: Ie304715c6ae6ce1336a21759d66ef4d60bd5f23e
    (Manually cherry picked from commit 5ce4d64150e2636da06d3fb61a20b20ced971cef)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/340014
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-rabbitmq_server/commit/?id=afe37cfc6141c5185d2550aa7aeaf67b63439b41
Submitter: Jenkins
Branch: stable/mitaka

commit afe37cfc6141c5185d2550aa7aeaf67b63439b41
Author: Jesse Pretorius <email address hidden>
Date: Wed May 4 10:47:26 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: Ibeaebc906262a7e5816048a002fe69c6bdd622e5
    (cherry picked from commit cf710222ca148ae71175ee71fa0c4e8539ccde42)

[OpenStack Infra (hudson-openstack)]

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)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/340009
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_glance/commit/?id=af6ac82212abc6b4f60c754bb1697bbaef6d619d
Submitter: Jenkins
Branch: stable/mitaka

commit af6ac82212abc6b4f60c754bb1697bbaef6d619d
Author: Jesse Pretorius <email address hidden>
Date: Wed May 4 09:52:14 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: Ide03340d3a03ded642040e27ccebca686f2b2b17
    (cherry picked from commit fc63481fc5763cf23163e802f0e529cff62cba39)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/340007
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_cinder/commit/?id=15245ceed4d2cd56fbd9b616d33b2f2b04ce0970
Submitter: Jenkins
Branch: stable/mitaka

commit 15245ceed4d2cd56fbd9b616d33b2f2b04ce0970
Author: Jesse Pretorius <email address hidden>
Date: Wed May 4 09:49: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

    Change-Id: I67d938d14bcaed0fa869e43cd94dfd884fd26fe3
    (cherry picked from commit c763bacab6a080b7aedbf35ea4ed40a25ab29ca0)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/340003
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_horizon/commit/?id=cd6521fbd875d937e7e6c921843102cd2dcf2714
Submitter: Jenkins
Branch: stable/mitaka

commit cd6521fbd875d937e7e6c921843102cd2dcf2714
Author: Jesse Pretorius <email address hidden>
Date: Wed May 4 10:33:53 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: Ia4b35ffc76d256d47dba128e8a6e00f55a9c5f88
    (cherry picked from commit bc92d064f4a2ec91f344cf29233522b9fa9b5079)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/340012
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=cc50cb1e66538b401b647fbba07ea8c43d74f579
Submitter: Jenkins
Branch: stable/mitaka

commit cc50cb1e66538b401b647fbba07ea8c43d74f579
Author: Jesse Pretorius <email address hidden>
Date: Wed May 4 10:35:31 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: I78eabbb51d4711bc01da9f224be7089ff5eb81e2
    (cherry picked from commit b3cca27a9e92bcbec2deafd04ba92cc2b69d21fd)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/340016
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_aodh/commit/?id=be35b2a09e8d953288c7aff3ee7255c28125f95c
Submitter: Jenkins
Branch: stable/mitaka

commit be35b2a09e8d953288c7aff3ee7255c28125f95c
Author: Jesse Pretorius <email address hidden>
Date: Wed May 4 09:44:24 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: Iebff3c8e9d215898ee07632c101931910327a52e
    (cherry picked from commit c2603d83b8adca396215d2de35319e0f3c569356)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/340010
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_ceilometer/commit/?id=591d1f3f5e9c7ec11b701f63600438d50158a92b
Submitter: Jenkins
Branch: stable/mitaka

commit 591d1f3f5e9c7ec11b701f63600438d50158a92b
Author: Jesse Pretorius <email address hidden>
Date: Wed May 4 09:48:26 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: Idb3f0c0ff8468eec330b4b39dcce567af0b1f9ef
    (cherry picked from commit dee286cb9498d2f4bd13c84d99159346eb7999e5)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/340015
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_ironic/commit/?id=a6e7556ca9326fdf577aff0f07cdb96b046926b9
Submitter: Jenkins
Branch: stable/mitaka

commit a6e7556ca9326fdf577aff0f07cdb96b046926b9
Author: Jesse Pretorius <email address hidden>
Date: Wed May 4 09:42:39 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: I75eb265b9634d7c2524d48212c9a2af2c39dc128
    (cherry picked from commit 7823efb09c510dd30a9b55a814cff76b52d5bdfe)

[OpenStack Infra (hudson-openstack)]

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)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/340011
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_swift/commit/?id=be11ed00df30cde3b6b657d35f337c97948d2d3b
Submitter: Jenkins
Branch: stable/mitaka

commit be11ed00df30cde3b6b657d35f337c97948d2d3b
Author: Jesse Pretorius <email address hidden>
Date: Wed May 4 10:43:41 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: Id04b2f74831e3422b036308c638be5428509e57a
    (cherry picked from commit cf882feb534c74f3d53d854cd135d36f3abfe8be)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/340005
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=77505d75a4c3cc441d94ef92c8d92db9e1298e08
Submitter: Jenkins
Branch: stable/mitaka

commit 77505d75a4c3cc441d94ef92c8d92db9e1298e08
Author: Jesse Pretorius <email address hidden>
Date: Wed May 4 10:41: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

    Change-Id: I1d6f0123b81a0cfc20a6d30c1a87d1f861a473a7
    (cherry picked from commit 4c2b4b81bdf700919e41e0b7750172924d1a2012)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/340006
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-galera_server/commit/?id=7139fd2c6000a09c7cd44bc4acb8e3f1762e3968
Submitter: Jenkins
Branch: stable/mitaka

commit 7139fd2c6000a09c7cd44bc4acb8e3f1762e3968
Author: Jesse Pretorius <email address hidden>
Date: Wed May 4 09:41:00 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: I90a044e142829ea90bbc81cdda5a2a257fe8de22
    (cherry picked from commit ac3bbca051c5b87ddbe7cc1a477be013b0669f12)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/340020
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=d3121477179fe12a1aa2b2d4ffde4b12e4924367
Submitter: Jenkins
Branch: master

commit d3121477179fe12a1aa2b2d4ffde4b12e4924367
Author: Jean-Philippe Evrard <email address hidden>
Date: Sat Jul 9 15:37:35 2016 +0100

    Removed the default pip install options from upgrade.sh

    Instead of forcing to reinstall pip packages during an upgrade, we
    should instead make sure the environment always have the latest pip
    package version.

    This commit is part of a group of commits to ensure latest pip packages
    are installed in the venv (cf. topic pip-install-latest on gerrit) for
    the standard playbooks, and remove the options used by default in the
    upgrade script (pip_install_options=--force-reinstall)

    Closes-Bug: 1596620

    Change-Id: I9ce478217d806fe04a2fc25be4cd42a875a6ffa2
    Signed-off-by: Jean-Philippe Evrard <email address hidden>

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/342021

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/342021
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=4da3e98601b74852c61ee649eacff0bf1af3dee2
Submitter: Jenkins
Branch: stable/mitaka

commit 4da3e98601b74852c61ee649eacff0bf1af3dee2
Author: Jean-Philippe Evrard <email address hidden>
Date: Sat Jul 9 15:37:35 2016 +0100

    Removed the default pip install options from upgrade.sh

    Instead of forcing to reinstall pip packages during an upgrade, we
    should instead make sure the environment always have the latest pip
    package version.

    This commit is part of a group of commits to ensure latest pip packages
    are installed in the venv (cf. topic pip-install-latest on gerrit) for
    the standard playbooks, and remove the options used by default in the
    upgrade script (pip_install_options=--force-reinstall)

    Closes-Bug: 1596620

    Change-Id: I9ce478217d806fe04a2fc25be4cd42a875a6ffa2
    Signed-off-by: Jean-Philippe Evrard <email address hidden>
    (cherry picked from commit d3121477179fe12a1aa2b2d4ffde4b12e4924367)

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/343629

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/343629
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=413151fddc0701c1659ba691ecdccf4eec57c724
Submitter: Jenkins
Branch: master

commit 413151fddc0701c1659ba691ecdccf4eec57c724
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
    Change-Id: I6b6464d517497e461505f64dfd7256baff995653

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 14.0.0.0b2 development milestone.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 13.3.0 release.