Discovery fails with all-int project id during url fallback

[Monty Taylor]

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.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/621257
Committed: https://git.openstack.org/cgit/openstack/keystoneauth/commit/?id=4960c48aec24e7d1b0f436a704d63b9ec9b6b805
Submitter: Zuul
Branch: master

commit 4960c48aec24e7d1b0f436a704d63b9ec9b6b805
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: Id90b3b9e4852494a4678b0a9bb67362babdc971c

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/keystoneauth 3.11.2 release.