Bug 1442882 - aodh-base.yaml uses hard coded regionOne
Summary: aodh-base.yaml uses hard coded regionOne
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ga
: 12.0 (Pike)
Assignee: Pradeep Kilambi
QA Contact: Sasha Smolyak
URL:
Whiteboard:
Depends On:
Blocks: 1534540
TreeView+ depends on / blocked
 
Reported: 2017-04-17 21:48 UTC by Keith Schincke
Modified: 2018-02-05 19:07 UTC (History)
7 users (show)

Fixed In Version: openstack-tripleo-heat-templates-7.0.0-0.20170609153210.2f5f8fc.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1534540 (view as bug list)
Environment:
Last Closed: 2017-12-13 21:23:38 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 457373 0 None None None 2017-05-03 15:33:44 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Keith Schincke 2017-04-17 21:48:17 UTC 
Description of problem:
aodh::auth::auth_region in aodh-base.yaml is hardcoded to regionOne instead of using the available KeystoneRegion. This results in the /etc/aodh/aodh.conf configuration having the wrong region_name parameter

Version-Release number of selected component (if applicable):
Ocata and Newton

How reproducible:
100%

Steps to Reproduce:
1. Update custom environment to set KeystoneRegion to a value other than 'regionOne' (example: regionTwo)
2. Deploy overcloud
3. Examine deployed configuration

Actual results:

# egrep "regionOne|regionTwo" /etc/aodh/aodh.conf 
region_name = regionOne

Expected results:
# egrep "regionOne|regionTwo" /etc/aodh/aodh.conf 
region_name = regionTwo



Additional info:
Comment 5 Sasha Smolyak 2017-12-13 11:46:57 UTC 
The value of aodh region is not hardcoded anymore.
Verified
Comment 8 errata-xmlrpc 2017-12-13 21:23:38 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:3462
Note You need to log in before you can comment on or make changes to this bug.