heat-api-cfn endpoint is created to RegionOne instead of regionOne
When deploying, heat-api-cfn is assigned to RegionOne. This leads to a
bad user experience when logging into horizon, because if RegionOne is
selected by default, the users finds all menus empty (no computing, or
anything else).
Reviewed: https:/ /review. openstack. org/386666 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=74317f2b966 d6c91150cb33666 be7d15e2b31ffe
Committed: https:/
Submitter: Jenkins
Branch: master
commit 74317f2b966d6c9 1150cb33666be7d 15e2b31ffe
Author: Luca Lorenzetto <email address hidden>
Date: Fri Oct 14 17:27:44 2016 +0200
heat-api-cfn endpoint is created to RegionOne instead of regionOne
When deploying, heat-api-cfn is assigned to RegionOne. This leads to a
bad user experience when logging into horizon, because if RegionOne is
selected by default, the users finds all menus empty (no computing, or
anything else).
Thanks to trown for finding out the issue.
Closes-Bug: 1633524
Change-Id: Ic108280f6b0875 ffec10be6f69666 9962fb82e6b