Plugins » foreman-tasks

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1420651

Description of problem:

If you run "service foreman-tasks start", this will kick off foreman-tasks. However, "hammer ping" will return "fail" for foreman-tasks for a few dozen seconds after the systemctl script has returned. This makes it appear as if startup has failed.

After 10-30 seconds, "hammer ping" will show success for foreman-tasks, and things will operate normally. While this is a minor issue, the delay can be enough time for the user to think something is wrong and start checking log files, only to retry the hammer ping and get a success message.

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

Steps to Reproduce:
1. service foreman-tasks stop
2. service foreman-tasks start
3. hammer ping

Actual results:

candlepin:
Status: ok
Server Response: Duration: 19ms
candlepin_auth:
Status: ok
Server Response: Duration: 19ms
pulp:
Status: ok
Server Response: Duration: 26ms
foreman_tasks:
Status: FAIL
Server Response:

Expected results:

foreman_tasks should be successful immediately, or the service script should wait