pip-conf-removal.yml doesnt remove the older repo on all the containers
Bug #1627174 reported by
seetha
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
High
|
Jesse Pretorius |
Bug Description
pip-conf-
hosts: hosts:repo_all
Changed in openstack-ansible: | |
assignee: | nobody → seetha (munnangi2010) |
To post a comment you must log in.
Still working on reproducing this, but I think I see the logic where this might be needed or the role needs improvement.
The playbook installs the pip_lock_down role. /github. com/openstack/ openstack- ansible/ blob/stable/ mitaka/ playbooks/ galera- install. yml#L66
https:/
pip_lock_down depends on pip_install, so that's run first. /github. com/openstack/ openstack- ansible- pip_lock_ down/blob/ stable/ mitaka/ meta/main. yml#L32
https:/
The last task in pip_install installs pip_required_ pip_packages, which includes packages newly added to the Mitaka release. /github. com/openstack/ openstack- ansible- pip_install/ blob/stable/ mitaka/ tasks/main. yml#L124 /github. com/openstack/ openstack- ansible- pip_install/ blob/stable/ mitaka/ defaults/ main.yml# L46
https:/
https:/
pip_required_ pip_packages are only installed with the isolated flag if pip_packages needed to be installed that way.
So if the required versions of pip_packages are available, the fall back task isn't required and the "Install pip packages" task will fail.
Which tagged releases were used for Liberty and Mitaka?