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.
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'
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 ***