Bug 1811546

Summary:	LDAP backend default doesn't align to keystone defaults.
Product:	Red Hat OpenStack	Reporter:	Keigo Noha <knoha>
Component:	puppet-keystone	Assignee:	Dave Wilde <dwilde>
Status:	CLOSED ERRATA	QA Contact:	nlevinki <nlevinki>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	alee, dwilde, jagee, jjoyce, jschluet, lbragsta, rmascena, slinaber, tvignaud
Target Milestone:	z12	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	puppet-keystone-12.4.0-7.el7ost.src.rpm	Doc Type:	Known Issue
Doc Text:	Cause: puppet-keystone defaults override keystone defaults Consequence: unexpected settings applied to keystone.conf Workaround (if any): override the keystone parameter defaults in THT to the desired settings Result: expected keystone.conf generated	Story Points:	---
Clone Of:
Clones:	1814833 (view as bug list)		Environment:
Last Closed:	2020-06-24 11:33:20 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:
Bug Depends On:
Bug Blocks:	1814833

Description Keigo Noha 2020-03-09 08:13:40 UTC

Description of problem:
LDAP backend default doesn't align to keystone defaults.

For example, use_pool and use_user_pool is false in puppet-keystone.
However, keystone's default configuration is true.

Also there are so many undef assignment to the parameters.

This is also found at upstream puppet-keystone.

Version-Release number of selected component (if applicable):
Current puppet-keystone

How reproducible:
Always

Steps to Reproduce:
1. Try to configure ldap backend.
2. Check keystone.conf.
3.

Actual results:
Some parameters aren't same as keystone's default.

Expected results:
Not assigned parameters by T-H-T should be the same as keystone's defaults.

Additional info:

Comment 21 errata-xmlrpc 2020-06-24 11:33:20 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/RHBA-2020:2718