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:
I'm not sure what the problem is, but I currently run into issues starting the katello service via RPM install. That said, it appears to start, but a status shows me that it's really not running.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

[root@dhcp231-182 ~]# service katello start
Starting katello:                                          [  OK  ]
[root@dhcp231-182 ~]# service katello status
katello is not running.
  
Actual results:
it says it starts [OK] but a status indicates that's really not running

Expected results:
do some sort of sanity test upon startup to assure the service is actually running and stable before giving the green light.


Additional info:

Yeah we currently run the katello in nohup temporary. The plan is to switch to 

[root@nec-em15 katello-utils]# service katello start
Starting katello: [  OK  ]
[root@nec-em15 katello-utils]# service katello status
katello is not running.
[root@nec-em15 katello-utils]# service katello status
katello is not running.

...wait few more seconds...

[root@nec-em15 katello-utils]# service katello status
katello is running.

Temporary solution was to add sleep 5s to the init script. We are changing the way of starting katello in few weeks.

0dfb601 725495 - katello service should return a valid result

@Corey - it this workaround does not work for you, ping me and we could accelerate our production setup discussion. Or I could provide better fix for that.

Works for me. QA Verified.

getting rid of 6.0.0 version since that doesn't exist