Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
DescriptionMartin Bacovsky
2018-09-05 11:58:07 UTC
Currently we use hammer ping in Checks::HammerPing and remap the resources back to services. This approach if quite fragile, works only on server and can miss some failing services.
Since recently foreman maintain is aware of the services installed on the system and we can leverage this in the check.
How to reproduce:
# systemctl stop foreman-proxy
# foreman-maintain health check
Running ForemanMaintain::Scenario::FilteredScenario
================================================================================
Check for verifying syntax for ISP DHCP configurations: [SKIPPED]
DHCP feature is not enabled
--------------------------------------------------------------------------------
Check whether system is self-registered or not: [OK]
--------------------------------------------------------------------------------
The health check is positive even when the proxy service does not run. This should be the very basic feature and should work since beginning.
Comment 5Satellite Program
2018-09-11 18:02:29 UTC
Upstream bug assigned to mbacovsk
Comment 6Satellite Program
2018-09-11 18:02:33 UTC
Upstream bug assigned to mbacovsk
Comment 7Satellite Program
2018-09-17 18:02:39 UTC
VERIFIED
Version tested:
# rpm -qa | grep maintain
rubygem-foreman_maintain-0.2.10-1.el7sat.noarch
[root@qe-capsule-feature-rhel7 ~]# systemctl stop foreman-proxy
[root@qe-capsule-feature-rhel7 ~]# foreman-maintain health check
Running ForemanMaintain::Scenario::FilteredScenario
================================================================================
Check for verifying syntax for ISP DHCP configurations: [SKIPPED]
DHCP feature is not enabled
--------------------------------------------------------------------------------
Check whether all services are running: [FAIL]
Following services are not running: foreman-proxy
--------------------------------------------------------------------------------
Continue with step [Restart applicable services]?, [y(yes), n(no), q(quit)] y
Restart applicable services:
Stopping the following service(s):
foreman-proxy
\ stopping foreman-proxy
Redirecting to /bin/systemctl stop foreman-proxy.service
| All services stopped
Starting the following service(s):
foreman-proxy
\ starting foreman-proxy
Redirecting to /bin/systemctl start foreman-proxy.service
| All services started [OK]
--------------------------------------------------------------------------------
Rerunning the check after fix procedure
Check whether all services are running: [OK]
--------------------------------------------------------------------------------
Check whether system is self-registered or not: [OK]
--------------------------------------------------------------------------------
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/RHBA-2018:2926