#51106 Healthcheck code DSBLE0002 not returned on disabled suffix
Closed: wontfix by spichugi. Opened by mreynolds.

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

Description of problem:
DSBLE0002 should be returned when suffix is disabled.
But running healthcheck returns only the warning message and it stops checking
other components.
Version-Release number of selected component (if applicable):
389-ds-base-1.4.3.8-2.module+el8.3.0+6591+ebfc9766.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Create a new root suffix:
# ldapmodify -a -p 389 -h localhost -D "cn=Directory manager" -w password
dn: cn="dc=test,dc=com",cn=mapping tree, cn=config
objectclass: top
objectclass: extensibleObject
objectclass: nsMappingTree
nsslapd-state: backend
nsslapd-backend: userData
cn: dc=test,dc=com
2. Add a database for this suffix :
# ldapmodify -a -p 389 -h localhost -D "cn=Directory manager" -w password
dn: cn=userdata,cn=ldbm database,cn=plugins,cn=config
objectclass: extensibleObject
objectclass: nsBackendInstance
nsslapd-suffix: dc=test,dc=com
3. Disable the suffix
# ldapmodify -p 389 -h localhost -D "cn=Directory manager" -w password
dn: cn="dc=test,dc=com",cn=mapping tree,cn=config
changetype: modify
replace: nsslapd-state
nsslapd-state: disabled
Actual results:
# dsctl instance healthcheck
Beginning lint report, this could take a while ...
Checking Backends ...
Error: Operations error - Warning: Operation attempted on a disabled node :
dc=test,dc=com
Expected results:
DS Lint Error: DSBLE0002
-------------------------------------------------------------------------------
-
Severity: HIGH
Affects:
 -- dc=test,dc=com
Details:
-----------
Unable to query the backend.  LDAP error ({'desc': 'Operations error', 'info':
'Warning: Operation attempted on a disabled node : dc=test,dc=com\n'})
Resolution:
-----------
Check the server's error and access logs for more information.
Additional info:

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

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)
- Issue tagged with: Healthcheck

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

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
- Issue status updated to: Closed (was: Open)

Metadata