Project

General

Profile

Actions

Bug #21294

closed

foreman-tasks startup returns quickly, but "hammer ping" shows failed state until startup is complete

Added by Adam Ruzicka over 6 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Dynflow
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

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

Actions #1

Updated by Adam Ruzicka over 6 years ago

  • Category set to Dynflow
  • Target version set to 113

Per discussion this should probably be done by caching executor's state and answering ping requests using the cache

Actions #2

Updated by Adam Ruzicka over 5 years ago

  • Status changed from New to Closed
  • Triaged set to No
  • Pull request https://github.com/Dynflow/dynflow/pull/255 added
Actions #3

Updated by Ivan Necas over 5 years ago

  • Status changed from Closed to New
  • Pull request deleted (https://github.com/Dynflow/dynflow/pull/255)

Mistakenly marked as fixed previously: this issue is still there

Actions #4

Updated by Adam Ruzicka about 3 years ago

  • Status changed from New to Closed

With the move to sidekiq-based workers we are starting the services with type=notify, meaning the service should appear as "up" after it is fully started.

Actions

Also available in: Atom PDF