Keystone clients cannot be configured for internal endpoint

Bug #2060194 reported by Andrew Bonney
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
New
Undecided
Unassigned

Bug Description

We have found in our tests of Magnum+CAPI that the Keystone client code lacks the ability to select anything other than the public endpoint for accessing Keystone.

We are using a hard-coded workaround in our deployment which demonstrates where this is causing an issue: https://github.com/bbc/magnum/commit/b0c67736ccdb17e991cb7006c0664998b64d5c24

For 'neutron_client', 'nova_client' and similar we set the 'endpoint_type' to 'internalURL'. Whilst 'keystone_authtoken' 'interface' is set to the default (internal), this doesn't appear to be referenced by this code path.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.