Murano not select correctly the endpoint when there are several regions

Bug #1479260 reported by Henar Muñoz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Murano
Fix Released
Medium
Henar Muñoz

Bug Description

When the Cloud has several regions, Murano selects the endpoint of the first region returned by keystone. The idea is that by configuration a default region is specified. If there isn't any one, the selection will be as before

Changed in murano:
assignee: nobody → Henar Muñoz (henar-munozfrutos)
status: New → In Progress
Changed in murano:
importance: Undecided → Medium
milestone: none → liberty-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to murano (master)

Reviewed: https://review.openstack.org/206940
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=0fb5b904f9b8d3d3002f7bfd55b55a3fb0fc3439
Submitter: Jenkins
Branch: master

commit 0fb5b904f9b8d3d3002f7bfd55b55a3fb0fc3439
Author: Henar Muñoz Frutos <email address hidden>
Date: Wed Jul 29 10:46:52 2015 +0200

    Default Region Configuration Property

    It provides a configuration property region_name_for_services which contains
    a default region name used to get services endpoints in the case that they are
    several regions

    Closes Bug: #1479260

    Change-Id: I8ca3ee5aebd54c177b958327fdaa5906aa6a4cb2

Changed in murano:
status: In Progress → Fix Committed
Changed in murano:
status: Fix Committed → Fix Released
Changed in murano:
milestone: liberty-3 → 1.0.0
Changed in murano:
milestone: 1.0.0 → 1.0.1
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.