#47913 remove-ds.pl should not remove /var/lib/dirsrv
Closed: wontfix None Opened 6 years ago by edewata.

The /var/lib/dirsrv is owned by the 389-ds-base RPM and it's generally assumed that the folder will always exist as long as the RPM is installed.

%dir %{_localstatedir}/lib/%{pkgname}

Some applications such as IPA are using this folder various purposes (e.g. home directory for DS user, storing boot.ldif). The problem is currently the remove-ds.pl will delete this folder if it's removing the last DS instance.

# remove /var/lock/dirsrv & /var/run/dirsrv if this was the last instance
if(!<$pkglockdir/*>){
    rmdir $pkglockdir;
    rmdir $pkgrundir;
    rmdir $pkglibdir;
}

This could create problems to other applications (e.g. IPA installation will fail) since the above assumption will no longer be true. The remove-ds.pl should not remove any folder created by the RPM. The folder should only be removed when uninstalling the RPM.

The setup-ds.pl currently will create the /var/lib/dirsrv folder, but it shouldn't be necessary since the folder is created automatically during RPM installation.


The original reason these directories were removed was because if you create a new instance owned by a different user that new instance will fail to start because of ownership issues with these /var directories. So this still needs to be taken into account when addressing this ticket.

See https://fedorahosted.org/389/ticket/47394

no cloning, upstream tests can cover this.

578f946..afd7699 master -> master
commit afd7699
Author: Mark Reynolds mreynolds@redhat.com
Date: Tue Jun 9 17:10:20 2015 -0400

Metadata Update from @mreynolds:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.3.4.0

4 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1244

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

8 months ago

Login to comment on this ticket.

Metadata