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.
Bug 2012911 - named journalctl logs shows 'zone testrealm.test/IN: serial (serialnumber) write back to LDAP failed.'
Summary: named journalctl logs shows 'zone testrealm.test/IN: serial (serialnumber) wr...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: ipa
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: Sudhir Menon
URL:
Whiteboard:
Depends On:
Blocks: 2027125
TreeView+ depends on / blocked
 
Reported: 2021-10-11 15:09 UTC by Sudhir Menon
Modified: 2022-11-15 10:32 UTC (History)
7 users (show)

Fixed In Version: ipa-4.9.10-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 10:00:08 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-7121 0 None None None 2021-10-20 14:22:28 UTC
Red Hat Issue Tracker RHELPLAN-100367 0 None None None 2021-10-20 14:22:32 UTC
Red Hat Product Errata RHBA-2022:7988 0 None None None 2022-11-15 10:00:33 UTC

Description Sudhir Menon 2021-10-11 15:09:54 UTC 
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:
Comment 3 Rob Crittenden 2021-10-20 14:22:20 UTC 
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?
Comment 8 Rob Crittenden 2022-05-25 19:49:26 UTC 
The ipa-healthcheck tests run after the IPA server is configured and the packages are installed/uninstalled during the test.

This was failing in some environments which lacked full DNSSEC support.

We disabled this for the healthcheck tests in upstream ticket https://pagure.io/freeipa/issue/9151

master: https://pagure.io/freeipa/c/92d8077304ad0847c42eca3d11c79d9e22a46335
ipa-4-9: https://pagure.io/freeipa/c/f11b7b3bf50f7ccf4689b1b0f80894b0b1247983

I think we can link them and move this into POST.
Comment 13 Sumedh Sidhaye 2022-07-18 06:53:51 UTC 
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.
Comment 17 errata-xmlrpc 2022-11-15 10:00:08 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.