RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1348903 - slapd.InstScriptsEnabled=false does not check for the existing instance script directory.
Summary: slapd.InstScriptsEnabled=false does not check for the existing instance scrip...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.3
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: wibrown@redhat.com
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-22 09:36 UTC by Amita Sharma
Modified: 2016-12-05 02:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-05 02:38:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Amita Sharma 2016-06-22 09:36:56 UTC 
Description of problem:
slapd.InstScriptsEnabled=false does not check for the existing instance script directory.

Version-Release number of selected component (if applicable):
389-ds-base-1.3.5.6-1.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Do setup-ds.pl and create an instance named -> slapd-instance
2. Go to /usr/lib64/dirsrv/slapd-instance
3. execute remove-ds.pl -a -f -i slapd-instance
[root@mgmt7 slapd-instance]# remove-ds.pl -a -f -i slapd-instance
cannot remove path when cwd is /usr/lib64/dirsrv/slapd-instance for /usr/lib64/dirsrv/slapd-instance:  at /usr/lib64/dirsrv/perl/DSCreate.pm line 1426.
The following errors occurred during removal:
Error: could not remove path '/usr/lib64/dirsrv/slapd-instance'.  Error: No such file or directory

NOTE:: Script directory is not removed because of the above error(human error) /usr/lib64/dirsrv/slapd-instance.

4. Now, Reinstall the directory with same ID and with slapd.InstScriptsEnabled=false ::
setup-ds.pl slapd.InstScriptsEnabled=false

Instance script directory still exists. which is misleading.


Actual results:
Instance script directory exists even if slapd.InstScriptsEnabled=false is given.

Expected results:
It should complain about the existing instance script directory which is there already due to human error/previous removal error.

Additional info:
It is a corner case, but leads to inconsistent behavior.
Note You need to log in before you can comment on or make changes to this bug.