#50883 Health check tool FSChecks fails on the instance without TLS
Closed: wontfix by mreynolds. Opened by vashirov.

Issue Description

If an instance is configured without TLS, health check for FSChecks fails:

INFO: Checking FSChecks ...
DEBUG: Retrieving entry with [('cn=config',)]
DEBUG: Retrieved entry [dn: cn=config
nsslapd-certdir: /etc/dirsrv/slapd-master1
]
DEBUG: [Errno 2] No such file or directory: '/etc/dirsrv/slapd-master1/pin.txt'
Traceback (most recent call last):
  File "/usr/sbin/dsctl", line 134, in <module>
    result = args.func(inst, log, args)
  File "/workspace/ds/src/lib389/lib389/cli_ctl/health.py", line 89, in health_check_run
    result = lo_inst.lint()
  File "/workspace/ds/src/lib389/lib389/dseldif.py", line 355, in lint
    for result in fn():
  File "/workspace/ds/src/lib389/lib389/dseldif.py", line 364, in _lint_file_perms
    perms = int(oct(os.stat(ds_file['name'])[ST_MODE])[-3:])
FileNotFoundError: [Errno 2] No such file or directory: '/etc/dirsrv/slapd-master1/pin.txt'
ERROR: Error: [Errno 2] No such file or directory: '/etc/dirsrv/slapd-master1/pin.txt'

Package Version and Platform

389-ds-base-1.4.3.2-20200205gitfcd6b2e1c.fc31.x86_64

Steps to reproduce

from lib389.topologies import topology_m2
def test_m2(topology_m2):
    breakpoint()
# dsctl master1 healthcheck

Actual results

# dsctl master1 healthcheck
Enter password for cn=Directory manager on ldap://localhost:39001:
Beginning lint report, this could take a while ...
Checking Backends ...
Checking Config ...
Checking FSChecks ...
Error: [Errno 2] No such file or directory: '/etc/dirsrv/slapd-master1/pin.txt' 

Expected results

DS healt check tool should not fail if TLS is not configured and pin.txt is not present.


Fixing this in https://pagure.io/389-ds-base/issue/50882

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: duplicate
- 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/3936

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

Metadata