Sahara dashboard client use is antithetical to proper discovery

[Jeremy Freudberg]

Instead of letting keystoneauth do as it's supposed to, it looks up the endpoint from the catalog independently. That would be fine, except nowadays what's in the catalog is not necessarily the final versioned url.

So, things are poised to break now that we are starting to recommend that deployments start transitioning to the unversioned endpoint in catalog as part of APIv2 work.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/536683
Committed: https://git.openstack.org/cgit/openstack/sahara-dashboard/commit/?id=8f2dfd7a8fd816e76fc522fb3d5a5d5b4a2197ce
Submitter: Zuul
Branch: master

commit 8f2dfd7a8fd816e76fc522fb3d5a5d5b4a2197ce
Author: Jeremy Freudberg <email address hidden>
Date: Tue Jan 23 06:09:12 2018 +0000

    Don't try to predetermine the Sahara URL

    Because guess what, times have changed. When that code was written
    version discovery wasn't what it is today...

    Without this change, we couldn't handle unversioned endpoints in the
    service catalog.

    Closes-Bug: #1745083

    Change-Id: Ie82e8a67b2820909625719c5f8a39ca0e1e2fbc0

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/sahara-dashboard 8.0.0.0rc1 release candidate.