Unblock tooz gate

We have a couple of issues blocking tooz test jobs right now. This
is a combination of two commits that fix the problem.

Cap grpcio<1.16.0

1.16.0 introduces a bug that is causing our etcd3 tests to fail on
a consistent basis. Until that is resolved we can't use any higher
versions of grpcio.

1.0.0 is used as the lower bound on the assumption that any version
of the current major release will work. Since we weren't setting a
bound before that seems relatively safe.

Partial-Bug: 1808046

Fix requirements

The requirements check job is failing on a couple of the entries in
this project. enum34 needs a lower bound, and futurist has an
exclusion that isn't in global-requirements.

enum34 is given the same lower bound as oslo.upgradecheck, and
futurist's lower bound is increased to the last global lower bound
(before lower bounds were removed), which eliminates the need for
the exclusion.

Change-Id: I1b279e138325b596f5ec2c61717029d2f7bdd075
Depends-On: https://review.openstack.org/#/c/624759/
This commit is contained in:
Ben Nemec 2018-12-11 21:59:24 +00:00
parent 77f6bc516f
commit 70f144abde
1 changed files with 3 additions and 2 deletions

View File

@ -4,12 +4,13 @@
pbr>=1.6 # Apache-2.0
stevedore>=1.16.0 # Apache-2.0
six>=1.9.0 # MIT
enum34;python_version=='2.7' or python_version=='2.6' or python_version=='3.3' # BSD
enum34>=1.0.4;python_version=='2.7' or python_version=='2.6' or python_version=='3.3' # BSD
voluptuous>=0.8.9 # BSD License
msgpack>=0.4.0 # Apache-2.0
fasteners>=0.7 # Apache-2.0
tenacity>=3.2.1 # Apache-2.0
futures>=3.0;python_version=='2.7' or python_version=='2.6' # BSD
futurist!=0.15.0,>=0.11.0 # Apache-2.0
futurist>=1.2.0 # Apache-2.0
oslo.utils>=3.15.0 # Apache-2.0
oslo.serialization>=1.10.0 # Apache-2.0
grpcio>=1.0.0,<1.16.0