Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1069210

Summary:	External watchdog expires when time is moved month backward or forward
Product:	[Retired] Beaker	Reporter:	David Spurek <dspurek>
Component:	beah	Assignee:	beaker-dev-list
Status:	CLOSED DUPLICATE	QA Contact:	tools-bugs <tools-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	develop	CC:	aigao, asaha, dapospis, dcallagh, dspurek, ebenes, jjaburek, llim, rmancy
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-24 22:22:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Spurek 2014-02-24 13:22:08 UTC

Description of problem:
External watchdog expires when time is moved a month backward or forward. System time is changed back at the end of the same phase.



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


How reproducible:


Steps to Reproduce:
1.run test in beaker where time is changed a month backward or forward.
2.
3.

Actual results:


Expected results:


Additional info:
See job https://beaker.engineering.redhat.com/tasks/executed?recipe_task_id=19347261&recipe_task_id=19347273 for example of previously mentioned problem.

Comment 1 Dalibor Pospíšil 2014-02-24 13:59:03 UTC

The watchdog should use an independent or semi-independent time measurement. Something like 'timeout=10; while let timeout--; do sleep 1; done' instead of something like 'sleep $timeout'

Comment 3 Dan Callaghan 2014-02-24 22:22:50 UTC

The external watchdog is unaffected by the system clock (the external watchdog is managed by Beaker). The problem you are seeing is presumably bug 639255, where the harness does not correctly handle shifts in the system clock.

*** This bug has been marked as a duplicate of bug 639255 ***