Ensure that pip lock down happens before other dependencies
The pip_install role is depended on by a lot of other roles, and therefore sometimes gets processed prior to the pip_lock_down role resulting in the pip, setuptools and wheels packages being installed from a source other than the repo server once the repo server is available. This is not the intended behaviour - the repo server should always be a the primary source once it's available. This patch ensures that the pip_lock_down role is applied before all the other dependent roles to ensure that the expected behaviour is followed. Change-Id: I4cecb48a9ff9015905f3d65b312ebad4efcd9085
This commit is contained in:
parent
fabe88c625
commit
2e55d2c981
@ -30,11 +30,11 @@ galaxy_info:
|
|||||||
- development
|
- development
|
||||||
- openstack
|
- openstack
|
||||||
dependencies:
|
dependencies:
|
||||||
- apt_package_pinning
|
|
||||||
- openstack_openrc
|
|
||||||
- role: pip_lock_down
|
- role: pip_lock_down
|
||||||
when:
|
when:
|
||||||
- not swift_developer_mode | bool
|
- not swift_developer_mode | bool
|
||||||
- role: pip_install
|
- role: pip_install
|
||||||
when:
|
when:
|
||||||
- swift_developer_mode | bool
|
- swift_developer_mode | bool
|
||||||
|
- apt_package_pinning
|
||||||
|
- openstack_openrc
|
||||||
|
Loading…
Reference in New Issue
Block a user