Bug 1357579
| Summary: | python-tripleoclient isn't setting the proper region for identity in tempest-deployer-input.conf | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Arx Cruz <acruz> |
| Component: | python-tripleoclient | Assignee: | Martin Magr <mmagr> |
| Status: | CLOSED ERRATA | QA Contact: | tkammer |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 9.0 (Mitaka) | CC: | afazekas, dmatthew, dmellado, hbrock, jason.dobies, jjoyce, jschluet, jslagle, mburns, mcornea, mmagr, morazi, psedlak, rhel-osp-director-maint, rhos-maint, tkammer, tvignaud |
| Target Milestone: | async | Keywords: | Automation |
| Target Release: | 9.0 (Mitaka) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-tripleoclient-2.0.0-4.el7ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-08 20:06:31 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: | |
| Embargoed: | |||
|
Description
Arx Cruz
2016-07-18 14:46:53 UTC
I believe this should be a bug in tripleo-heat-templates. The proposed patch in the bug description (at the bottom of the text) changes the default there.
A workaround would be to use an extra heat environment and pass that to openstack overcloud deploy. An example of how to do this looks like this:
parameter_defaults:
NuageNovaRegionName: RegionOne
KeystoneRegion: RegionOne
ControllerExtraConfig: RegionOne
ceilometer::agent::auth::auth_region: 'RegionOne'
aodh::auth::auth_region: 'RegionOne'
gnocchi::auth::auth_region: 'RegionOne'
As noted on the upstream review, this has the potential to cause issues with upgrades, changing the region on a deployed system from regionOne to RegionOne. I don't know all the consequences, but this needs to be tested extensively (and even if it passes, I don't know that we'd want to do this). Customers could be driving some of their own operations/queries/etc off of the regionOne name and our changing could negatively impact their custom scripts. Instead of changing the default value, can we consider simply updating the tempest.conf generation to regionOne rather than using it's default or (even better) make the tempest.conf generation read this value from tht? Ok, BZ just refreshed my list of comment. Now I get why we cannot change wrong default. (In reply to Dougal Matthews from comment #8) > parameter_defaults: > NuageNovaRegionName: RegionOne > KeystoneRegion: RegionOne > ControllerExtraConfig: RegionOne > ceilometer::agent::auth::auth_region: 'RegionOne' > aodh::auth::auth_region: 'RegionOne' > gnocchi::auth::auth_region: 'RegionOne' This alone will probably not do all the necessary things, as the region name isn't an overcloud stack output, and the endpoints are configured via os-cloud-config at the moment. (In reply to Mike Burns from comment #10) > As noted on the upstream review, this has the potential to cause issues with > upgrades, changing the region on a deployed system from regionOne to > RegionOne. I don't know all the consequences, but this needs to be tested > extensively (and even if it passes, I don't know that we'd want to do this). Yes the patch would almost surely not work on upgrades as it is, we'd need to change the upgrade workflow to make it re-apply endpoint creation and possibly add one more step to delete the old endpoints once the cloud is up and running using the new endpoints. And another patch to os-cloud-config would be necessary too. I'm not sure if there could be other potential side effects of switching to a different region name on an existing cloud besides endpoints changing. > > Customers could be driving some of their own operations/queries/etc off of > the regionOne name and our changing could negatively impact their custom > scripts. +1 > > Instead of changing the default value, can we consider simply updating the > tempest.conf generation to regionOne rather than using it's default or (even > better) make the tempest.conf generation read this value from tht? I found http://docs.openstack.org/developer/tempest/sampleconf.html Could we do something like crudini --set /path/to/my/tempest.conf identity region regionOne to make tempest work? (The default is in TripleO for a long time, how have we been running tempest on TripleO until now?) Maybe changing the region name is worth looking into in the long term (?), but as written above, we don't have all the pieces at the moment, and it is probably an invasive operation. 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://rhn.redhat.com/errata/RHBA-2017-0470.html |