kayobe/etc
Pierre Riteau 2c7deb4be7 Fix multiple CI failures
1. Use stable/queens as version of kolla-ansible in ansible tests

Instead of always checking out the master branch, use the kolla-ansible
branch with which this Kayobe version is meant to be used.

This is based on change I074d4b9d444649ecf956d3cd92748862e8c89a5c,
though we cannot use {{ openstack_branch }} which was introduced with
Stein. We hardcode stable/queens instead, as we did in stable/rocky with
change I344b1e90d34e0c8e2fb30331038b296ac89449b1.

2. Install python-openstackclient using upper constraints

Detect current branch from .gitreview and use upper constraints to
install python-openstackclient, to guarantee compatibility with the
Python version in use. This is cherry picked from commit
ef33e6ecb7.

3. Update packages in virtualenvs

Kayobe uses a number of virtual environments on the remote hosts for
python dependencies such as shade, python-openstackclient, docker, etc.
By default these are stored in /opt/kayobe/venvs/. Typically we do not
provide version restrictions when installing these packages, so over the
course of time they may become stale and incompatible.

This change installs the latest version of packages allowed by OpenStack
upper constraints.

It also adds a new variable, 'pip_upper_constraints_file', to set the
upper constraints file. The existing variable
'kolla_upper_constraints_file' now defaults to the value of
'pip_upper_constraints_file'.

This is cherry picked from commit
ddfd6b6202.

4. Remove upgrade jobs from Zuul configuration

Upgrade jobs are failing because stable/pike has the same issues fixed
in kolla-ansible for stable/queens:

- https://review.opendev.org/#/c/717276/
- https://review.opendev.org/#/c/717302/

Fixing kayobe for stable/pike would involve fixing kolla-ansible for
stable/pike, which is not maintained anymore. Drop upgrade jobs instead.

Change-Id: Ie44508fe3d3b08190afa5a43748e43548a63ff82
2020-04-07 10:18:55 +02:00
..
kayobe Fix multiple CI failures 2020-04-07 10:18:55 +02:00