Mistral can't authenticate if keystone is singleton and region_name is in config

[Nikolay Makhotkin]

It is impossible now to use new multi-regional support feature if CONF.keystone_authtoken.region_name is specified but keystone service is deployed as a singleton (on top of all regions).

So, eventually, on every request mistral responses 500 and the error is:

  Can not find admin keystone endpoint for region_name and service_type.

One of the possible solutions is to introduce a separate region config parameter for actions (say, call it "default_region") and place it in different config section.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/466297
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=c3050df5ac169ef19062a353b050c411eff8efbc
Submitter: Jenkins
Branch: master

commit c3050df5ac169ef19062a353b050c411eff8efbc
Author: Nikolay Mahotkin <email address hidden>
Date: Fri May 19 17:21:34 2017 +0300

    Get rid of ambiguity in region_name

     Now keystone_authtoken.region_name is used
     both for requesting admin keystone endpoint
     and default region for openstack actions.
     Default region doesn't work for environments
     with keystone in 1 region and mistrals in many
     regions.

     Due to above just specifying default_region name
     separately for openstack actions can solve the problem

    Closes-Bug: #1691660

    Change-Id: I1eeea298feca45de37d77d791e1548ec5e7161a1

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/mistral 5.0.0.0b2 development milestone.