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: named journalctl logs shows 'zone testrealm.test/IN: serial (serialnumber) write back to LDAP failed.'
Version-Release number of selected component (if applicable):
ipa-server-4.9.6-9.el9_b
How reproducible: Always
Steps to Reproduce:
1. Installed IPA server
2. Install ipa-healthcheck package
Actual results:
Sep 20 20:00:04 master.testrealm.test named[36243]: zone testrealm.test/IN: loaded serial 1695254403
Sep 20 20:01:03 master.testrealm.test named[36243]: zone testrealm.test/IN: serial (1695254463) write back to LDAP failed
Sep 20 20:01:03 master.testrealm.test named[36243]: zone testrealm.test/IN: serial (1695254464) write back to LDAP failed
Sep 20 20:01:04 master.testrealm.test named[36243]: zone testrealm.test/IN: serial (1695254465) write back to LDAP failed
Sep 20 20:01:04 master.testrealm.test named[36243]: zone testrealm.test/IN: serial (1695254466) write back to LDAP failed
Sep 20 20:01:04 master.testrealm.test named[36243]: zone testrealm.test/IN: serial (1695254467) write back to LDAP failed
Sep 20 20:01:04 master.testrealm.test named[36243]: zone testrealm.test/IN: serial (1695254468) write back to LDAP failed
Sep 20 20:01:04 master.testrealm.test named[36243]: zone testrealm.test/IN: serial (1695254469) write back to LDAP failed
Sep 20 20:01:05 master.testrealm.test named[36243]: zone testrealm.test/IN: serial (1695254470) write back to LDAP failed
Sep 20 20:01:05 master.testrealm.test named[36243]: zone testrealm.test/IN: serial (1695254471) write back to LDAP failed
Sep 20 20:01:05 master.testrealm.test named[36243]: zone testrealm.test/IN: serial (1695254465) write back to LDAP failed
Expected results:
Fix the above issue.
Additional info:
The message "write back to LDAP failed" comes from bind-dyndb-ldap when it tries to update the serial number. Unfortunately it doesn't log the LDAP error.
We may be able to determine that if we have the 389-ds access log. Do you know if it's available?
Verification using latest RHEL9.1 nightly compose
ipa-client-4.10.0-2.el9.x86_64
ipa-client-common-4.10.0-2.el9.noarch
ipa-common-4.10.0-2.el9.noarch
ipa-healthcheck-core-0.9-9.el9.noarch
ipa-selinux-4.10.0-2.el9.noarch
ipa-server-4.10.0-2.el9.x86_64
ipa-server-common-4.10.0-2.el9.noarch
ipa-server-dns-4.10.0-2.el9.noarch
ipa-server-trust-ad-4.10.0-2.el9.x86_64
"write back to LDAP failed" message is not seen named and journal logs.
Attaching named and journal logs for reference.
Marking Bugzilla based on above observations.
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 (ipa 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-2022:7988