Wrong pip package versions after upgrade

[Jordan Callicoat]

If an environment is upgraded to a new release, pip packages from the old requirements.txt will remain installed even if the new requirements.txt requires previous or conflicting package versions.

10.1.3 requirements.txt has:

Jinja2==2.7.3
PyYAML==3.11

10.1.11 requirements.txt has:

Jinja2<=2.7.2
PyYAML>=3.1.0,<=3.10

Upgraded 10.1.11 environment has:

root@87b035a9-infra1:/opt/os-ansible-deployment/rpc_deployment# pip freeze | fgrep -e Jinja -e PyYAML
You are using pip version 6.1.1, however version 7.1.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Jinja2==2.7.3
PyYAML==3.11

Though this bug is reported with the above packages, it applies to *all* pip packages where versions in requirements.txt have changed between tags.

I tried passing -e pip_install_options="--force-reinstall" when running setup-everything, but I still have the newer versions of the packages.

[Nolan Brubaker (nolan-brubaker)]

Has this demonstrated improper behavior? Does the install fail, or does it break services?

[Jordan Callicoat (jcallicoat)]

"Incomplete (Reporter, Give Us More Information!)

This is the status around which the Bug Janitor’s expiration code works. It is an intermediate stage between New and Confirmed; it means that someone has looked at the bug, attempted to understand or reproduce it, and needs more information to be able to confirm it is in fact a bug."

What further information do you need about this bug? Is there some scenario where you intend the wrong packages to be installed after an upgrade?

[Jesse Pretorius (jesse-pretorius)]

This is a real issue between many tags due to upstream requirements changes and cap changes all the time.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit 2c19010ff9a936c5d0ad3d72e2015308c105ff0f
Author: Jesse Pretorius <email address hidden>
Date: Wed Sep 30 12:48:13 2015 +0100

    Allow pip extra arguments to be passed to playbooks

    This patch adds the variable 'pip_install_options' which is passed to the pip
    install module as extra arguments in order to allow the use of options like
    '--force-reinstall' when executing playbooks.

    eg: openstack-ansible -e pip_install_options="--force-reinstall" \
            setup-openstack.yml

    This is required due to constant upstream changes in dependencies which
    result in python wheel version upgrades and downgrades between tagged
    versions of openstack-ansible.

    The intention is that this can be used whenever a deployer switches between
    tags for both upgrades and downgrades.

    DocImpact
    Closes-Bug: #1489251
    Closes-Bug: #1499451
    Related-Bug: #1501114
    Change-Id: I996185e009a4c4af4f23798619bdbd0d490360c9

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/229542
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=f5e3b1171f41ff10b60725c7c30d13a18f3156ca
Submitter: Jenkins
Branch: kilo

commit f5e3b1171f41ff10b60725c7c30d13a18f3156ca
Author: Jesse Pretorius <email address hidden>
Date: Wed Sep 30 12:48:13 2015 +0100

    Allow pip extra arguments to be passed to playbooks

    This patch adds the variable 'pip_install_options' which is passed to the pip
    install module as extra arguments in order to allow the use of options like
    '--force-reinstall' when executing playbooks.

    eg: openstack-ansible -e pip_install_options="--force-reinstall" \
            setup-openstack.yml

    This is required due to constant upstream changes in dependencies which
    result in python wheel version upgrades and downgrades between tagged
    versions of openstack-ansible.

    The intention is that this can be used whenever a deployer switches between
    tags for both upgrades and downgrades.

    DocImpact
    Closes-Bug: #1489251
    Closes-Bug: #1499451
    Related-Bug: #1501114
    Change-Id: I996185e009a4c4af4f23798619bdbd0d490360c9
    (cherry picked from commit 2c19010ff9a936c5d0ad3d72e2015308c105ff0f)

[Jesse Pretorius (jesse-pretorius)]

For Juno, the pip install options can already be used - so closing this bug for Juno as invalid.

[Davanum Srinivas (DIMS) (dims-v)]

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

[Doug Hellmann (doug-hellmann)]

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

[Davanum Srinivas (DIMS) (dims-v)]

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