#48323 lib389 assertion causes issues when instance is named differently to directory.
Closed: wontfix None Opened 5 years ago by firstyear.

It's possible to create a ds instance where instance directory names are not the same as the instance name. In lib389 there is an assertion that attempts to make sure these are the same, even though that may not necessarily be true.


May I have a use case for this RFE? -- It's possible to create a ds instance where instance directory names are not the same as the instance name.

I think that I actually want to backout of this enhancement: I have found many places in setup-ds.pl where if your configdir name doesn't match the instance name, things will begin to break in subtle ways as there is an expectation that the two are always identical.

So we either accept this patch and try to look for other areas where instance name != configdir name (IE slapd-<name>) to make this rare use case work, or we leave this check in place, and use it to catch out people doing this, which at the moment apparently is only myself.

It's too complicated to fix all the places this assumption is made. For now, I believe that we should state that /etc/dirsrv/slapd-<name> must match <instance name> else issues will arise.

Milestone lib389 1.0 deleted

Metadata Update from @nhosoi:
- Issue assigned to firstyear

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/1654

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: Invalid)

a year ago

Login to comment on this ticket.

Metadata