Discovery fails with all-int project id during url fallback
Bug #1806109 reported by
Monty Taylor
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| keystoneauth |
Fix Released
|
Medium
|
Monty Taylor | ||
Bug Description
On clouds, such as Rackspace Public Cloud, that have both an inaccessible discovery document and an integer project id, the "parse version from url" fallback logic fails because the int project id in the url parses as a valid (if very large) version.
Granted, it's a perfect storm of:
- non-standard int project ids
- non-standard blocking of discovery document
- out-dated project id in URL
but it just fails in epicly bad ways.
| Changed in keystoneauth: | |
| assignee: | nobody → Monty Taylor (mordred) |
| status: | New → In Progress |
| Changed in keystoneauth: | |
| importance: | Undecided → Medium |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to keystoneauth (master) | #1 |
| Changed in keystoneauth: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/keystoneauth 3.11.2 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 4960c48aec24e7d
Author: Monty Taylor <email address hidden>
Date: Fri Nov 30 12:39:58 2018 -0600
Fix version discovery for clouds with int project_ids
On a cloud that has inaccessible version discovery documents AND uses
integer project ids, the discovery fallback logic can fail because the
project id parses as a (very large) version.
Check to see that the url segment in the fallback code begins with a v,
so that we're only attempting to parse versions from actual candidate
segments.
Closes-Bug: #1806109
Change-Id: Id90b3b9e485249