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.
+++ This bug was initially created as a clone of Bug #2099484 +++
Description of problem: IPADNSSystemRecordsCheck displays warning message for 2 expected ipa-ca AAAA records.
Version-Release number of selected component (if applicable):
ipa-server-4.9.8-8.module+el8.7.0+14711+1e093de3.x86_64
How reproducible: Always.
Steps to Reproduce:
1. Install IPA server and replica with ca having both --ip-address=ipv4-address and --ip-address=ipv6-address
2. Run ipa-healthcheck tool for IPADNSSystemRecordsCheck and check the result.
Actual results:
Although IPA Server and replica both are having IPV6 address assigned to CA, the healthcheck tool complains that only one entry is present.
#ipa-healthcheck --failures-only
{
"source": "ipahealthcheck.ipa.idns",
"check": "IPADNSSystemRecordsCheck",
"result": "WARNING",
"uuid": "5fe925f2-6bd5-411c-9a0d-352d850b792c",
"when": "20220617143708Z",
"duration": "0.038578",
"kw": {
"msg": "Got {count} ipa-ca A records, expected {expected}",
"count": 1,
"expected": 2
}
Expected results:
Fix the WARNING message displayed.
Additional info: Logging this bug to have it tracked for 8.7 release.
Upstream issue has already been logged.
https://github.com/freeipa/freeipa-healthcheck/issues/270
--- Additional comment from Sudhir Menon on 2022-06-21 06:06:00 UTC ---
Adding Flo's observation on the pagure ticket.
The issue happens when IPv4 or IPv6 is configured on one server but not on all the servers.
Relevant code:
freeipa-healthcheck/src/ipahealthcheck/ipa/idns.py
195 ca_count = 0
196 for server in system_records.servers_data:
197 master = system_records.servers_data.get(server)
198 if 'CA server' in master.get('roles'):
199 ca_count += 1
200
201 if len(answers) != ca_count:
freeipa-healthcheck/src/ipahealthcheck/ipa/idns.py
230 ca_count = 0
231 for server in system_records.servers_data:
232 master = system_records.servers_data.get(server)
233 if 'CA server' in master.get('roles'):
234 ca_count += 1
235
236 if len(answers) != ca_count:
ca_count is incremented for each server with the CA role, not considering that the server could have either IPv4 or IPv6 disabled.
The code assumes all-or-nothing: if one server has an IPv4 address, all the other ones are expected to also have an IPv4 address
and ipa-ca should contain an A record for each server with the CA role. Same for IPv6.
Pre-verified both manually and using the automation (as I was not sure whether it was properly covered)
ipa-healthcheck-0.12-1.el9.noarch
# main and replica server setup with both IPs
# ipa-healthcheck --check IPADNSSystemRecordsCheck --source ipahealthcheck.ipa.idns
[]
Therefore marking as pre-verified, tested.
Verified manually as there are currently issues with the automation (pending investigation).
1. set up main server with ipa-server-install --domain dom-$(hostname -f) --realm DOM-$(hostname -f | tr '[:lower:]' '[:upper:]') -a Secret123 -p Secret123 --ip-address=ipv4 --ip-address=ipv6 -U
2. set up client, upgrade client to replica
3. [on main] ipa-healthcheck --check IPADNSSystemRecordsCheck --source ipahealthcheck.ipa.idns
[]
Issue not present, therefore markins 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 (ipa-healthcheck 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-2023:2381