#8834 RFE: report NOT_CONFIGURED (or similar string) instead of SUCCESS when a check's target is not configured
Closed: invalid by rcritten. Opened by pcech.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1776296

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:

Metadata Update from @pcech:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1776296

Issue linked to bug 1776296

Closing because opened in the wrong tracker.

Will not fix in freeipa-healthcheck because NOT_CONFIGURED is not a state of success/failure but of configuration.

Metadata Update from @rcritten:
- Issue close_status updated to: invalid
- Issue status updated to: Closed (was: Open)

Metadata