Bug 1778643 - [RHEL8 beaker]: Can not report panic when kernel have "invalid opcode" panic
Summary: [RHEL8 beaker]: Can not report panic when kernel have "invalid opcode" panic
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: lab controller
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 27.1
Assignee: Renan Rodrigo Barbosa
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-02 09:01 UTC by xiaoli feng
Modified: 2020-01-29 08:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-05 10:46:10 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Beaker Project Gerrit 6698 0 'None' MERGED Add 'kernel BUG' line to panic detection regex 2020-01-29 08:00:17 UTC

Description xiaoli feng 2019-12-02 09:01:32 UTC 
Description of problem:
In this beaker job https://beaker.engineering.redhat.com/jobs/3916445. I met a panic. But the beaker didn't report panic. Maybe should improve the condition for panic.

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

How reproducible:
Just met once panic

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


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