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:
service foreman status returns non-zero error code for success
It says "PASSED" but returns "1" 

Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140711.0

How reproducible:
100%

Steps to Reproduce:
1. service foreman status
Foreman is running under passenger[PASSED]

2. echo $?
1

Actual results:
It says "PASSED" but returns "1" 

Expected results:
When it says "PASSED" it should return "0"

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

The "1" is to indicate it can't even tell you what the status is, though LSB says this should actually be "4".  Zero would be even more misleading I think.

Created redmine issue http://projects.theforeman.org/issues/7023 from this bug

If it can't even tell me the status why then it writes 'is running' ???

Per 6.3 planning, moving out non acked bugs to the backlog

I do not envision this bug being addressed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.