#51144 Dsctl healthcheck doesn't work when using instance name with 'slapd-'
Closed: wontfix by mreynolds. Opened by mreynolds.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1806573

Description of problem:
When running # dsctl slapd-inst1 healthcheck, it reports an error :
Error: [Errno 2] No such file or directory:
'/etc/dirsrv/slapd-slapd-inst1/dse.ldif'
Version-Release number of selected component (if applicable):
389-ds-base-1.4.2.8-2
How reproducible:
Always
Steps to Reproduce:
1.Install an instance inst1 of DS
2.List the existing instances :
# dsctl -l
slapd-inst1
3.Run # dsctl slapd-inst1 healthcheck
Actual results:
Beginning lint report, this could take a while ...
Checking Backends ...
Checking Config ...
Checking Encryption ...
Checking FSChecks ...
Checking ReferentialIntegrityPlugin ...
Checking MonitorDiskSpace ...
Checking Replica ...
Checking Changelog5 ...
Checking DSEldif ...
Error: [Errno 2] No such file or directory:
'/etc/dirsrv/slapd-slapd-inst1/dse.ldif'
Expected results:
Healthcheck checks all items and ends without error
Additional info:

Metadata Update from @mreynolds:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1806573

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue priority set to: normal
- Issue set to the milestone: 1.4.2 (was: 0.0 NEEDS_TRIAGE)

Commit 3a964c2d relates to this ticket

Commit 3a964c2 relates to this ticket

a681b444e..946b5e1d3 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

46b51b806..56e97a4e1 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

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

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

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)

Metadata
Related Pull Requests