Comment 6 for bug 1473396

@Cathrine no it doesn't make sense to do that as a separate thing. We just need to remove the hardcoded endpoint type and it should just use the same mechanisms that already exist. If we did anything where a client initialized with a credentials of a certain type had a different endpoint type then what was configured we'd be conflating the concept of roles assigned to a user and endpoint type. Just to make it clear there is no coupling between the concept of roles and endpoint type defined anywhere. Any restrictions where certain operations or roles only work on certain endpoint type is 100% a deployment specific and not something we can really account for in tempest because there are too many possibilities.

The fix here is literally just:

http://paste.openstack.org/show/378822/ (and the sample config update)

If you need to use publicURL for your testing, just change the config opt to that and you'll be good to go. The only bug here is that adminURL was hard coded.

For what you're trying to do in your test that's perfectly fine. The test just needs to be written so it allocates a regular user (which implies non-admin) from the credential provider and inits the clients with those creds, which it should do automatically if the inheritance is setup correctly. Nothing, about the endpoint type or the client needs to be special cased for the tests in that review.