RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
Restarting the crond service needlessly reports failure if the service wasn't running before.

Version-Release number of selected component (if applicable):
cronie-1.4.4-7.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Make sure crond isn't running
2. service crond restart
  
Actual results:
# service crond restart
Stopping crond: [FAILED]
Starting crond: [  OK  ]

Expected results:
# service crond restart
Starting crond: [  OK  ]

Additional info:
Restarting a stopped service should just start it without making an impression of something failing.

Created attachment 520101 [details]
Don't report a misleading failure on restart

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: BZ#733697 - Service restart needlessly reports failure
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

Starting crond: [  OK  ]
:: [ 05:49:43 ] :: [ INFO    ] :: rlRun: command = 'service crond restart'; exitcode = 0; expected = 0
:: [   PASS   ] :: Running 'service crond restart' (Expected 0, got 0)
:: [   PASS   ] :: File '/var/tmp/tmp.y162y8Ozf2' should not contain 'FAILED':: :: [   LOG    ] :: Duration: 1s
:: [   LOG    ] :: Assertions: 2 good, 0 bad
:: [   PASS   ] :: RESULT: BZ#733697 - Service restart needlessly reports failure

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.

http://rhn.redhat.com/errata/RHBA-2013-1681.html