Bug 1752849
| Summary: | Incorrect message is displayed when ipa-healthcheck tool is run with --output-type=human | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Sudhir Menon <sumenon> |
| Component: | ipa-healthcheck | Assignee: | Rob Crittenden <rcritten> |
| Status: | CLOSED ERRATA | QA Contact: | ipa-qe <ipa-qe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.1 | CC: | fcami, frenaud, ksiddiqu, pcech, ssidhaye |
| Target Milestone: | rc | Keywords: | TestCaseProvided |
| Target Release: | 8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ipa-healthcheck-0.4-1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-04-28 15:43:29 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
Sudhir Menon
2019-09-17 12:06:13 UTC
Merged upstream in master: https://github.com/freeipa/freeipa-healthcheck/commit/28124d70d40c1cdd77eec46d8a547802eb2f9444 Build used for verification: [root@master ~]# rpm -q ipa-server ipa-healthcheck ipa-server-4.8.4-4.module+el8.2.0+5591+1f878b19.x86_64 ipa-healthcheck-0.4-4.module+el8.2.0+5489+95477d9f.noarch [root@master ~]# Verification steps: 1. Install IPA server and ipa-healthcheck tool 2. Run ipactl stop 3. Now run the command ipa-healthcheck --source ipahealthcheck.meta.services --output-type=human 4. Check the message displayed on the console. [root@master ~]# cat /etc/redhat-release Red Hat Enterprise Linux release 8.2 Beta (Ootpa) [root@master ~]# ipactl stop Stopping ipa-otpd Service Stopping pki-tomcatd Service Stopping ipa-custodia Service Stopping httpd Service Stopping kadmin Service Stopping krb5kdc Service Stopping Directory Service ipa: INFO: The ipactl command was successful [root@vmaster ~]# ipa-healthcheck --source ipahealthcheck.meta.services --output-type=human SUCCESS: ipahealthcheck.meta.services.certmonger ERROR: ipahealthcheck.meta.services.dirsrv: dirsrv: not running SUCCESS: ipahealthcheck.meta.services.gssproxy ERROR: ipahealthcheck.meta.services.httpd: httpd: not running ERROR: ipahealthcheck.meta.services.ipa_custodia: ipa-custodia: not running ERROR: ipahealthcheck.meta.services.ipa_otpd: ipa-otpd: not running ERROR: ipahealthcheck.meta.services.kadmin: kadmin: not running ERROR: ipahealthcheck.meta.services.krb5kdc: krb5kdc: not running ERROR: ipahealthcheck.meta.services.pki_tomcatd: pki_tomcatd: not running SUCCESS: ipahealthcheck.meta.services.sssd Based on the above observations marking Bugzilla verified. Test added upstream in ipatests/test_integration/test_ipahealthcheck.py::TestIpaHealthCheck::test_human_output master: https://pagure.io/freeipa/c/4a3b7baed785f7492e8404dac3eee8a8ce9fd937 upstream test: ipa-4-8: https://pagure.io/freeipa/c/7974ac9f8c7969df85f689d94f5b30c18e661daa Automated test passing in CI ------------------------------ Captured log call ------------------------------- transport.py 391 INFO RUN ['systemctl', 'stop', 'sssd'] transport.py 513 DEBUG RUN ['systemctl', 'stop', 'sssd'] transport.py 217 DEBUG Exit code: 0 transport.py 391 INFO RUN ['ipa-healthcheck', '--source', 'ipahealthcheck.meta.services', '--check', 'sssd', '--output-type', 'human'] transport.py 513 DEBUG RUN ['ipa-healthcheck', '--source', 'ipahealthcheck.meta.services', '--check', 'sssd', '--output-type', 'human'] transport.py 558 DEBUG ERROR: ipahealthcheck.meta.services.sssd: sssd: not running transport.py 217 DEBUG Exit code: 1 transport.py 391 INFO RUN ['systemctl', 'start', 'sssd'] transport.py 513 DEBUG RUN ['systemctl', 'start', 'sssd'] transport.py 217 DEBUG Exit code: 0 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, 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/RHEA-2020:1640 |