Bug 1713361

Summary:	Update defaults.inf
Product:	Red Hat Enterprise Linux 7	Reporter:	Viktor Ashirov <vashirov>
Component:	389-ds-base	Assignee:	mreynolds
Status:	CLOSED ERRATA	QA Contact:	RHDS QE <ds-qe-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.7	CC:	ebock, lkrispen, nkinder, rmeggins, spichugi, tbordaz, vashirov
Target Milestone:	rc
Target Release:	7.7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sync-to-jira
Fixed In Version:	389-ds-base-1.3.9.1-9.el7	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-06 12:59:38 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 Viktor Ashirov 2019-05-23 13:22:13 UTC

Description of problem:
When running tests, lib389 complains:
E   KeyError: 'Invalid defaults.inf, missing key tmpfiles_d'

Please backport https://pagure.io/389-ds-base/c/1088afbb3d645a6a068aab301a0a04db8e9e1e9c?branch=389-ds-base-1.3.9 to the downstream build.

Comment 1 Viktor Ashirov 2019-05-23 13:31:03 UTC

Another issue with defaults.inf:
In 1.3.9:

inst_dir = @serverdir@

In master:

inst_dir = @serverdir@/slapd-{instance_name}

The latter is the correct one. Otherwise, lib389's remove_ds_instance() is destructive and deletes /usr/lib64/dirsrv, which contains perl modules and 389-ds-base libraries.

Comment 2 Viktor Ashirov 2019-05-23 13:35:10 UTC

This inst_dir issue was fixed in https://pagure.io/389-ds-base/pull-request/49760, needs a backport to 1.3.9.

Comment 3 Viktor Ashirov 2019-05-23 13:56:36 UTC

I filed a separate PR to address this issue: https://pagure.io/389-ds-base/pull-request/50402

Comment 4 Viktor Ashirov 2019-05-29 15:30:42 UTC

Fixed upstream, moving to POST.

Comment 8 errata-xmlrpc 2019-08-06 12:59:38 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-2019:2152