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:
The value of aodh region is not hardcoded anymore. Verified
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