Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
verified:tested (see comment 6) with build 389-ds-1.4-8040020201125182123.866effaa / 389-ds-base-libs-1.4.3.16-2.module+el8.4.0+8803+fd0f8fe3.x86_64
-> marking as VERIFIED
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (389-ds:1.4 bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2021:1835
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: