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.

Bug 1780358

Summary: ipa-healthcheck - Check if the CA renewal master is reachable.
Product: Red Hat Enterprise Linux 8 Reporter: Têko Mihinto <tmihinto>
Component: ipaAssignee: Thomas Woerner <twoerner>
Status: CLOSED WONTFIX QA Contact: ipa-qe <ipa-qe>
Severity: low Docs Contact:
Priority: low    
Version: 8.1CC: pasik, pcech, rcritten, tscherf
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-17 08:00:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Têko Mihinto 2019-12-05 18:36:14 UTC
Description of problem:
ipa-healthcheck should report if the configured CA renewal master is reachable.

Version-Release number of selected component (if applicable):
# rpm -qa | grep ipa-server
ipa-server-common-4.8.0-11.module+el8.1.0+4247+9f3fd721.noarch
ipa-server-4.8.0-11.module+el8.1.0+4247+9f3fd721.x86_64
#

How reproducible:
Always.

Steps to Reproduce:
1. Change the RDN of the LDAP entry cn=<CA_RENEWAL_MASTER>,cn=masters,cn=ipa,cn=etc,dc=<DOMAIN> to a value that points to a non-existing server.

2. Run the command
# ipa-healthcheck  --source ipahealthcheck.ipa.roles --check IPARenewalMasterCheck


Actual results:
The command shows that the server is not a CA renewal master. 

# ipa-healthcheck  --source ipahealthcheck.ipa.roles --check IPARenewalMasterCheck
[
  {
    "source": "ipahealthcheck.ipa.roles",
    "check": "IPARenewalMasterCheck",
    "result": "SUCCESS",
    "uuid": "29ef3a25-81bb-4a9b-aa56-dd27743936b1",
    "when": "20191205175059Z",
    "duration": "0.156789",
    "kw": {
      "key": "renewal_master",
      "master": false
    }
  }
]
#  

Expected results:
It would be nice to also show if there is a reachable CA renewal master.
Eg:

# ipa-healthcheck  --source ipahealthcheck.ipa.roles --check IPARenewalMasterCheck
[
  {
    "source": "ipahealthcheck.ipa.roles",
    "check": "IPARenewalMasterCheck",
    "result": "SUCCESS",
    "uuid": "3431e60b-c98a-4633-a7f9-249747b1a1b8",
    "when": "20191205175326Z",
    "duration": "0.161224",
    "kw": {
      "key": "renewal_master",
      "master": false,
      "current_master": "unreachable_master.example.com",
      "current_master_reachable": false
    }
  }
]


Additional info:

Comment 2 Rob Crittenden 2019-12-05 19:33:39 UTC
Interesting idea. Generally speaking we like to keep all checks local because it gets complicated fast to search remote machines without adding healthcheck-specific credentials. But checking to see if a host is reachable should be doable.

Comment 3 Rob Crittenden 2020-03-04 19:24:14 UTC
Thinking about it further, what is the purpose of checking if the renewal master is reachable?

It isn't a requirement for it to be so. The certs are distributed using normal IPA replication so there need not be a direct link between any other masters with the renewal master.

There are RFE's asking to be able to limit connectivity between certain masters so if this were checked it could lead to false positives.

Comment 4 Têko Mihinto 2020-03-09 14:18:15 UTC
Hi Rob,

This RFE is actually to request a couple of additional information that could be useful for customers and Support.

1 - The first one is to provide the  FQDN of the CA renewal master ( in case it is not the host on which the ipa-healthcheck command is run )

2 - The second one is to let the user know if the CA renewal master is reachable.
It may happen it is not reachable due to mistakes.
For instance:
    * wrong DNS configuration ( this might be checked in the DNS plugin [1] )
    * decommission of a VM that is hosting the renewal master

IMHO, it would be nice to get the FQDN of the CA renewal master ( it is already provided with "ipa config-show" ).
Knowing whether it is reachable is less important but might be useful for Support folks.

Regards,
Têko.

[1] https://www.freeipa.org/page/V4/Healthcheck#DNS

Comment 5 Rob Crittenden 2020-03-10 18:28:01 UTC
I can do the first request since it is stored in configuration.

But not the second. It is not an error to be not reachable and could lead to false positives.

Comment 6 Têko Mihinto 2020-03-10 18:56:40 UTC
Hi Rob,

OK, that works for me :-)

Thanks,
Têko.

Comment 9 Petr Čech 2021-05-17 07:58:06 UTC
Upstream ticket:
https://pagure.io/freeipa/issue/8842

Comment 10 Petr Čech 2021-05-17 08:00:28 UTC
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. The request was cloned to the upstream tracker a long time ago (see link to the upstream ticket above), but it was unfortunately not given priority either in the upstream project, nor in Red Hat Enterprise Linux.

Given that this request is not planned for a close release, it is highly unlikely it will be fixed in this major version of Red Hat Enterprise Linux. We are therefore closing the request as WONTFIX.

To request that Red Hat reconsiders the decision, please reopen the Bugzilla with the help of Red Hat Customer Service and provide additional business and/or technical details about it's importance to you. Please note that you can still track this request or even offer help in the referred upstream Pagure ticket to expedite the solution.

FreeIPA Product Owner