Bug 2121747

Summary:	dscreate error, cannot start ns-slapd with custom db_dir path, incorrect sub dir permissions
Product:	Red Hat Directory Server	Reporter:	Pierre Rogier <progier>
Component:	Command Line Utilities	Assignee:	LDAP Maintainers <idm-ds-dev-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	LDAP QA Team <idm-ds-qe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	11.5	CC:	bsmejkal, idm-ds-dev-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-26 14:07:02 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 Pierre Rogier 2022-08-26 13:57:30 UTC

Description of problem:
   dscreate fails when using custom path with the db_dir parameter.


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


How reproducible: Always


Steps to Reproduce:
See reproduction steps in github 

Actual results:
  dscreate fails because newly created instance fails to start


Expected results:
  instance should be successfully started and dscreate should success.

Additional info:
  There are several issues related to how the filesystem directories are created within lib389/instance/setup.py: ( ownership, permission and selinux label are not properly set)

Comment 1 Pierre Rogier 2022-08-26 14:07:02 UTC


*** This bug has been marked as a duplicate of bug 1924569 ***