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.
Description of problem:
When checking services on the Satellite using 'foreman-maintain service status' the summary at the bottom shows "OK" when services are dead or inactive.
Version-Release number of selected component (if applicable):
6.4
How reproducible:
Everytime
Steps to Reproduce:
1. Start Satellite services
2. Systemctl stop httpd
3. Check services with 'foreman-maintain service status'
Actual results:
- displaying puppetserver
● puppetserver.service - puppetserver Service
Loaded: loaded (/usr/lib/systemd/system/puppetserver.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Wed 2018-09-05 10:49:29 EDT; 5s ago
Process: 7512 ExecStop=/opt/puppetlabs/server/apps/puppetserver/bin/puppetserver stop (code=exited, status=0/SUCCESS)
Process: 5576 ExecStart=/opt/puppetlabs/server/apps/puppetserver/bin/puppetserver start (code=exited, status=0/SUCCESS)
Main PID: 5607 (code=exited, status=143)
Sep 05 10:43:02 sat64htb.usersys.redhat.com systemd[1]: Starting puppetserver Service...
Sep 05 10:44:03 sat64htb.usersys.redhat.com systemd[1]: Started puppetserver Service.
Sep 05 10:49:28 sat64htb.usersys.redhat.com systemd[1]: Stopping puppetserver Service...
Sep 05 10:49:29 sat64htb.usersys.redhat.com systemd[1]: Stopped puppetserver Service.
- All services displayed [OK]
--------------------------------------------------------------------------------
Expected results:
- displaying puppetserver
● puppetserver.service - puppetserver Service
Loaded: loaded (/usr/lib/systemd/system/puppetserver.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Wed 2018-09-05 10:49:29 EDT; 5s ago
Process: 7512 ExecStop=/opt/puppetlabs/server/apps/puppetserver/bin/puppetserver stop (code=exited, status=0/SUCCESS)
Process: 5576 ExecStart=/opt/puppetlabs/server/apps/puppetserver/bin/puppetserver start (code=exited, status=0/SUCCESS)
Main PID: 5607 (code=exited, status=143)
Sep 05 10:43:02 sat64htb.usersys.redhat.com systemd[1]: Starting puppetserver Service...
Sep 05 10:44:03 sat64htb.usersys.redhat.com systemd[1]: Started puppetserver Service.
Sep 05 10:49:28 sat64htb.usersys.redhat.com systemd[1]: Stopping puppetserver Service...
Sep 05 10:49:29 sat64htb.usersys.redhat.com systemd[1]: Stopped puppetserver Service.
- All services displayed puppetserver: FAILED
--------------------------------------------------------------------------------
Additional info:
Comment 1Christian Marineau
2018-09-05 15:10:56 UTC
Additional observation, when a mandatory service is stopped like httpd:
katello-service will return a warning and also an exit status of "1" as expected
# katello-service status
# echo $?
1
foreman-maintain will not return any warning, and the exit status will be "0"
# foreman-maintain service status
# echo $?
0
It is very important for users to get the same behavior with the new tooling, so any monitoring or script in place can still work despite this change.
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