Wrong pip package versions after upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
High
|
Jesse Pretorius | ||
Juno |
Invalid
|
High
|
Unassigned | ||
Kilo |
Fix Released
|
High
|
Jesse Pretorius | ||
Trunk |
Fix Released
|
High
|
Jesse Pretorius |
Bug Description
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>
Upgraded 10.1.11 environment has:
root@87b035a9-
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_
Changed in openstack-ansible: | |
status: | New → Incomplete |
Has this demonstrated improper behavior? Does the install fail, or does it break services?