Bug 679196 - Local Watchdog does not fire in all cases
Summary: Local Watchdog does not fire in all cases
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Retired
Component: beah
Version: 0.7
Hardware: Unspecified
OS: Unspecified
unspecified
low vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard: Misc
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-21 21:00 UTC by Marian Csontos
Modified: 2019-04-03 11:45 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-03 11:44:25 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Marian Csontos 2011-02-21 21:00:37 UTC 
Description of problem:
When there is a reboot more than 30 minutes after the task started, local watchdog (LWD) does not trigger: the original KILLTIME will be used to compute uptime at which to start LWD handling. At that time it will be after External Watchdog has fired and recycled machine. We would see EWD without LWD.

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

How reproducible:
100%

Steps to Reproduce:
1. create a task which will sleep 30 minutes and calls rhts-reboot afterwards
2. let it enter infinite loop
  
Actual results:
EWD

Expected results:
LWD

Additional info:
Comment 1 Nick Coghlan 2012-10-17 04:33:57 UTC 
Bulk reassignment of issues as Bill has moved to another team.
Comment 3 Tomas Klohna 🔧 2019-04-03 11:44:25 UTC 
Closing the issue due to better harness available. Please use Restraint for your testing purposes. Feel free to reopen if you have the same issue with Restraint as well.
Note You need to log in before you can comment on or make changes to this bug.