Project

General

Profile

Actions

Bug #23926

closed

'hammer ping' can erroneously say foreman-tasks is down when its just busy

Added by Ivan Necas almost 6 years ago. Updated over 5 years ago.

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

Description

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

Description of problem:

If you run 'hammer ping' on a busy system, foreman-tasks may show as being dead if it is busy processing lots of tasks. This can result in confusion.

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

How reproducible: intermittent

Steps to Reproduce:
1. create a lot of tasks, for example lots of package profile uploads
2. check hammer ping frequently

Actual results: hammer ping will occasionally time out after 2 seconds and show 'FAIL' for foreman-tasks

Expected results: hammer ping only fails for foreman-tasks if something requires user intervention.

Additional info: This might be similar to https://bugzilla.redhat.com/show_bug.cgi?id=1420651 but I am not sure if it's the same root cause.


Related issues 1 (0 open1 closed)

Related to foreman-tasks - Bug #24119: Delayed executor is not initiated, when previos delayed executor gets invalidated during startupClosedIvan NecasActions
Actions #1

Updated by Ivan Necas over 5 years ago

  • Subject changed from 'hammer ping' can erroneously say foreman-tasks is down when its just busy to 'hammer ping' can erroneously say foreman-tasks is down when its just busy
  • Status changed from New to Closed
  • Pull request https://github.com/Dynflow/dynflow/pull/255 added

Fixed in https://github.com/Dynflow/dynflow/pull/255 by introducing heartbeat to the executors

Actions #2

Updated by Ivan Necas over 5 years ago

  • Related to Bug #24119: Delayed executor is not initiated, when previos delayed executor gets invalidated during startup added
Actions

Also available in: Atom PDF