Bug 1804409 - Report Abort Status when Local Watchdog expired
Summary: Report Abort Status when Local Watchdog expired
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Restraint
Classification: Retired
Component: general
Version: 0.1.44
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Carol Bouchard
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-18 18:26 UTC by Carol Bouchard
Modified: 2020-06-02 09:18 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-02 09:18:06 UTC


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Beaker Project Gerrit 6777 0 None NEW (BLOCKED)Report Task Abort Status when Local Watchdog Expires 2020-06-02 09:17:57 UTC

Description Carol Bouchard 2020-02-18 18:26:51 UTC
Description of problem:
User requested when local watchdog expires, that a status of "Aborted" be returned to beaker.  This enables the user to identify this error case.

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


How reproducible:


Steps to Reproduce:
1.  Create job that forces local watchdog to expire
2.
3.

Actual results:
Task status shows warning

Expected results:
Task status shows Aborted.  Also must continue executing 10_localwatchdog and 99_reboot.  This is reflected in Task results.

Additional info:


Note You need to log in before you can comment on or make changes to this bug.