Identity plugins always handle catalog failures

[Jamie Lennox]

Auth plugins were designed initially to paper over the old and new catalog styles where we expected a versioned or unversioned endpoint in the catalog. This was intentional as all the clients were doing some variety of this hack and we wanted to centralize this.

We are now in a position where we expect the catalog to be correct and that it is reasonable to fail a request when the catalog is wrong. We should allow services to make this call.

From the mailing list: http://lists.openstack.org/pipermail/openstack-dev/2017-February/112943.html

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/438788

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/438788
Committed: https://git.openstack.org/cgit/openstack/keystoneauth/commit/?id=3ce5cb4bf6edd755fbba885666700bd4592a0032
Submitter: Jenkins
Branch: master

commit 3ce5cb4bf6edd755fbba885666700bd4592a0032
Author: Jamie Lennox <email address hidden>
Date: Tue Feb 28 11:51:10 2017 +1100

    Add an allow_version_hack flag to session and identity plugins.

    Whilst historically we always wanted keystoneauth to do the most
    permissive thing and allow a versioned or unversioned entry in a service
    catalog there are now cases where we would prefer to fail when the
    catalog is misconfigured. This will allow a client to opt out of
    versioned catalog endpoints to insist that the deployment is correctly
    configured.

    Closes-Bug: #1668484
    Change-Id: Ided0e0c7409994f703175fe61bd4043b840bcf1e

[OpenStack Infra (hudson-openstack)]

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