Bug 1442882

Summary: aodh-base.yaml uses hard coded regionOne
Product: Red Hat OpenStack Reporter: Keith Schincke <kschinck>
Component: openstack-tripleo-heat-templatesAssignee: Pradeep Kilambi <pkilambi>
Status: CLOSED ERRATA QA Contact: Sasha Smolyak <ssmolyak>
Severity: low Docs Contact:
Priority: medium    
Version: 11.0 (Ocata)CC: aschultz, dbecker, jschluet, mburns, morazi, pkilambi, rhel-osp-director-maint
Target Milestone: gaKeywords: Triaged
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openstack-tripleo-heat-templates-7.0.0-0.20170609153210.2f5f8fc.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1534540 (view as bug list) Environment:
Last Closed: 2017-12-13 21:23:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1534540    

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:

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.

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.