Bug 679196

Summary:	Local Watchdog does not fire in all cases
Product:	[Retired] Beaker	Reporter:	Marian Csontos <mcsontos>
Component:	beah	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:	tools-bugs <tools-bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	0.7	CC:	bpeck, jburke, mcsontos, tklohna, tools-bugs, xtian
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	Misc
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-03 11:44:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.