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 1776296 - RFE: report NOT_CONFIGURED (or similar string) instead of SUCCESS when a check's target is not configured
Summary: RFE: report NOT_CONFIGURED (or similar string) instead of SUCCESS when a chec...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa-healthcheck
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Rob Crittenden
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-25 12:41 UTC by Sudhir Menon
Modified: 2021-05-11 10:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-11 10:47:09 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Pagure freeipa issue 8834 0 None None None 2021-05-11 10:45:15 UTC

Description Sudhir Menon 2019-11-25 12:41:39 UTC 
Description of problem: ipahealthcheck.ipa.trust checks displays status as "SUCCESS" even when trust is not present on the system.


Version-Release number of selected component (if applicable):
ipa-server-4.8.2-2.module+el8.2.0+4736+360582ce.x86_64
ipa-healthcheck-0.3-4.module+el8.1.0+4098+f286395e.noarch


How reproducible: Always.


Steps to Reproduce:
1. Install IPA server and donot establish trust.
2. Run ipa-healthcheck --source ipahealthcheck.ipa.trust

Actual results:
The checks displays the status as "SUCCESS" even when there is no trust established on the IPA system.


[root@master ipa]# ipa trust-find
----------------
0 trusts matched
----------------
----------------------------
Number of entries returned 0
----------------------------


[root@master ipa]#  ipa-healthcheck --source ipahealthcheck.ipa.trust --output-type=human
SUCCESS: ipahealthcheck.ipa.trust.IPATrustAgentCheck
SUCCESS: ipahealthcheck.ipa.trust.IPATrustDomainsCheck
SUCCESS: ipahealthcheck.ipa.trust.IPATrustCatalogCheck
SUCCESS: ipahealthcheck.ipa.trust.IPAsidgenpluginCheck
SUCCESS: ipahealthcheck.ipa.trust.IPATrustAgentMemberCheck
SUCCESS: ipahealthcheck.ipa.trust.IPATrustControllerPrincipalCheck
SUCCESS: ipahealthcheck.ipa.trust.IPATrustControllerServiceCheck
SUCCESS: ipahealthcheck.ipa.trust.IPATrustControllerConfCheck
SUCCESS: ipahealthcheck.ipa.trust.IPATrustControllerGroupSIDCheck
SUCCESS: ipahealthcheck.ipa.trust.IPATrustPackageCheck


Expected results:
Checks should display correct status accordingly when trust is not setup/established on the IPA system.

Additional info:
Comment 1 François Cami 2019-11-25 16:51:53 UTC 
Having no trust setup is not an issue at all and there is no reason to use WARNING/ERROR/CRITICAL in this case.
In other words the behavior is intended.
Closing as NOTABUG.
Comment 4 François Cami 2019-12-09 15:23:10 UTC 
Reopening as it would be a useful RFE for reuse from ansible-freeipa PoV even if the current behavior is not a bug.
Comment 8 Petr Čech 2021-05-11 10:45:13 UTC 
Upstream ticket:
https://pagure.io/freeipa/issue/8834
Comment 9 Petr Čech 2021-05-11 10:47:09 UTC 
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. The request was cloned to the upstream tracker (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.
Note You need to log in before you can comment on or make changes to this bug.