#50208 lib389 should detect instances based on dse.ldif not sysconfig
Closed: wontfix 4 years ago by firstyear. Opened 5 years ago by firstyear.

Issue Description

We should detect instance presence by dse.ldif presence not sysconfig.

  • Change dse.ldif to be the first file we write during setup (to guarantee remove always have a target)
  • Change the inst list in DirSrv to look for the dse.ldif not the /etc/sysconfig file

This would mean the only fixed location remaining in the server is /etc/dirsrv/slapd-instance. All other locations should be properly dynamic at that point :)


Metadata Update from @firstyear:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Metadata Update from @mreynolds:
- Issue status updated to: Open (was: Closed)

5 years ago

This introduced a regression for list "all". Please review this PR:

https://pagure.io/389-ds-base/pull-request/50271

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

5 years ago

F29 version (389-ds-base-1.4.0.26-1.fc29.x86_64) is completely broken without this fix.
dscreate creates an instance, but fails to start it, because of the missing environment file.
It's possible to "fix" it by modifying the .service file, but a more proper fix should be backported.
@mreynolds, could you please make a new build for F29? Thanks!

Metadata Update from @vashirov:
- Issue status updated to: Open (was: Closed)

4 years ago

b543627..4cf65b3 389-ds-base-1.4.0 -> 389-ds-base-1.4.0

Metadata Update from @firstyear:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

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

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)

3 years ago

Login to comment on this ticket.

Metadata