Bug 980357 - [RFE] Check for "Press (any key|enter) to continue" when systems fail to boot
Summary: [RFE] Check for "Press (any key|enter) to continue" when systems fail to boot
Keywords:
Status: CLOSED DUPLICATE of bug 952661
Alias: None
Product: Beaker
Classification: Retired
Component: lab controller
Version: 0.13
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-02 07:25 UTC by Nick Coghlan
Modified: 2018-02-06 00:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-22 23:05:12 UTC


Attachments (Terms of Use)

Description Nick Coghlan 2013-07-02 07:25:01 UTC
If a system has a hardware problem that causes it to emit a "Press any key to continue" message during boot, this will show up in Beaker as a string of aborted jobs. If those jobs aren't using appropriately marked distros (see bug 654299), then the system won't be automatically marked as broken.

This proposal is to add a new heuristic for automatically marking systems as broken:

1. The recipe is terminated by the external watchdog
2. The system doesn't reboot at all (install_start is never called on the lab controller)
3. The console log contains an entry matching one of the patterns:
"Press any key to continue"
"Press [Ee]nter to continue"
"Press <(.*)> to continue"

Such a heuristic could also be tweaked to detect the PXE boot menu coming up (indicating the machine isn't properly booting from the network).

This should be configurable in a similar fashion to the PANIC_REGEX definition (BOOT_HANG_REGEX, perhaps?).

Comment 1 Nick Coghlan 2013-09-03 03:49:33 UTC
Anaconda may also hang with its text UI displayed to ask a question. This shows up in the console log as an ASCII-art display window, containing at least an ASCII art "OK" box and a bottom row of instructions indicating how to navigate the controls with the keyboard.

Comment 2 Dan Callaghan 2014-01-22 23:05:12 UTC

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


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