[openstack-dev] [tripleo] CI promotion blockers

Julie Pichon jpichon at redhat.com
Tue Jan 2 16:38:49 UTC 2018

On 2 January 2018 at 16:30, Alex Schultz <aschultz at redhat.com> wrote:
> On Tue, Jan 2, 2018 at 9:08 AM, Julie Pichon <jpichon at redhat.com> wrote:
>> Hi!
>> On 27 December 2017 at 16:48, Emilien Macchi <emilien at redhat.com> wrote:
>>> - Keystone removed _member_ role management, so we stopped using it
>>> (only Member is enough): https://review.openstack.org/#/c/529849/
>> There's been so many issues with the default member role and Horizon
>> over the years, that one got my attention. I can see that
>> puppet-horizon still expects '_member_' for role management [1].
>> However trying to understand the Keystone patch linked to in the
>> commit, it looks like there's total freedom in which role name to use
>> so we can't just change the default in puppet-horizon to use 'Member'
>> as other consumers may expect and settle on '_member_' in their
>> environment. (Right?)
>> In this case, the proper way to fix this for TripleO deployments may
>> be to make the change in instack-undercloud (I presume in [2]) so that
>> the default role is explicitly set to 'Member' for us? Does that sound
>> like the correct approach to get to a working Horizon?
> We probably should at least change _member_ to Member in
> puppet-horizon. That fixes both projects for the default case.

Oh, I thought there was no longer a default and that TripleO was
creating the 'Member' role by itself? Fixing it directly in
puppet-horizon sounds ideal in general, if changing the default value
isn't expected to cause other issues.



> Thanks,
> -Alex
>> Julie
>> [1] https://github.com/openstack/puppet-horizon/blob/master/manifests/init.pp#L458
>> [2] https://github.com/openstack/instack-undercloud/blob/master/elements/puppet-stack-config/puppet-stack-config.yaml.template#L622

More information about the OpenStack-dev mailing list