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: Ic283b08a00ac57c854fefd66589a326721fa9d93
This commit is contained in:
Jesse Pretorius 2016-03-31 14:02:51 +01:00 committed by Jesse Pretorius (odyssey4me)
parent 99b13a14e5
commit 234d1fd0cc
1 changed files with 6 additions and 3 deletions

View File

@ -30,15 +30,18 @@ galaxy_info:
- development
- openstack
dependencies:
- role: pip_lock_down
when:
- not keystone_developer_mode | bool
- role: pip_install
when:
- keystone_developer_mode | bool
- role: apt_package_pinning
when:
- ansible_pkg_mgr == 'apt'
- role: galera_client
when:
- keystone_database_enabled | bool
- role: pip_lock_down
when:
- not keystone_developer_mode | bool
- role: memcached_server
when:
- "'memcache' in keystone_token_driver"