zuul/nodepool
Code Issues Proposed changes

Block 0.20.0 of openstacksdk

Browse Source 
There is a bug in Rackspace Public Cloud that causes keystoneauth to
fail doing discovery which 0.20.0 of openstacksdk exposes because it
starts using keystoneauth discovery directly. Until the keystoneauth fix
lands and is released, running nodepool with 0.20.0 of openstacksdk will
fail when attempting to use Rackspace Public Cloud.

Just for the record, this is due to the fact that Rackspace Public
Cloud:

- has invalid integer project ids
- still senselessly keeps them in the compute service URL
- blocks access to the compute discovery document

The keystone team are kindly accepting a workaround fix to keystoneauth
even though it is a workaround for what is a completely invalid setup.

Change-Id: I72ec16ecb7770d97aa5703bdcfd3e8b188c89f19
This commit is contained in:
Monty Taylor 2018-11-30 13:15:53 -06:00
parent d4325cf6ac
commit c2d410d9fe
No known key found for this signature in database
GPG Key ID: 7BAE94BC7141A594
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
requirements.txt
View File

@ -6,7 +6,9 @@ python-daemon>=2.0.4,<2.1.0
extras
statsd>=3.0
PrettyTable>=0.6,<0.8
openstacksdk>=0.17.2,!=0.18.0
# openstacksdk 0.20.0 exposes a bug in keystoneauth. The pin can be removed
# once keystoneauth1 has made a release
openstacksdk>=0.17.2,!=0.18.0,!=0.20.0
diskimage-builder>=2.0.0
voluptuous
kazoo