repo is caching wrong versions of pinned pip_install packages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
High
|
Jesse Pretorius | ||
Liberty |
Fix Released
|
High
|
Jesse Pretorius | ||
Mitaka |
Fix Released
|
High
|
Jesse Pretorius |
Bug Description
As illustrated below the repo is caching setuptools-
root@osdeploy-
Setting setuptools!
root@osdeploy-
setuptools-
openstack-
openstack-
openstack-
openstack-
pip_get_
--no-index
--find-links "{{ openstack_repo_url }}/os-releases/{{ openstack_release }}"
--trusted-host "{{ openstack_repo_url | netloc_no_port }}"
TASK: [pip_install | Install PIP] *******
failed: [aio1_galera_
stderr: Could not find a version that satisfies the requirement setuptools==25.1.1 (from versions: 25.1.3)
No matching distribution found for setuptools==25.1.1
stdout: Ignoring indexes: https:/
Collecting pip==8.1.2
Downloading http://
Collecting setuptools==25.1.1
msg: Task failed as maximum retries was encountered
src: https:/
version: 4f366c332d9f084
src: https:/
version: cff0a5592b783cf
OSA at stable/mitaka 5c8dd5bd8d7898e
Changed in openstack-ansible: | |
importance: | Critical → High |
Changed in openstack-ansible: | |
assignee: | nobody → Jesse Pretorius (jesse-pretorius) |
Given requirements.txt with this content:
setuptools==25.1.1
And constraints.txt with this content:
setuptools<=25.1.3
The execution of 'pip wheel -r requirements.txt -c constraints.txt' results in setuptools 25.1.3 being downloaded, which is not what is expected.
Confirming this bug - we'll have to implement an overwrite of upper-constraints for anything in global- requirements- pins.txt to ensure that the requirements and constraints match.