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

Bug 1623729

Summary:	Beaker recorded panic against the wrong task
Product:	[Retired] Beaker	Reporter:	Dan Callaghan <dcallagh>
Component:	general	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	rasibley
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-21 14:15:04 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 Dan Callaghan 2018-08-30 03:43:32 UTC

Description of problem:
In this self-test recipe:
https://beaker-devel.app.eng.bos.redhat.com/recipes/25796
the machine panicked twice.
Once, on shutdown after Anaconda finished the installation.
Then again on shutdown during the reboot sanity tests.
However Beaker only recorded one panic (the first one). It recorded it with the correct timestamp but it appears only in the *final* task of the recipe which is not when it happened.

Version-Release number of selected component (if applicable):
25.6.git.13.0ab761a09 

How reproducible:
unsure

Steps to Reproduce:
1. ???

Actual results:
Panic result recorded against the final task in the recipe

Expected results:
For a panic before the first task has begun executing, I am not sure of the expected behaviour. I thought it should be recorded against the first task but this may have changed due to the fact that we no longer mark the first task as started as soon as the installation begins.
https://git.beaker-project.org/cgit/beaker/commit/?id=53d54a5fbd15b282ce3310dfe3e9bf41d1d942c9

However the second panic should have surely been recorded against the task where it happened, 
/distribution/beaker/Sanity/reboot-tests.

Additional info:
Might be related to the external watchdog script and the panic recovery delay behaviour?

Comment 1 Rachel Sibley 2018-11-12 15:51:26 UTC

I've seen this twice already, the most recent case can be viewed in this job:
https://beaker.engineering.redhat.com/jobs/3074938

The panic occurred during the first boot after kickstart, but isn't reported until later on during the final beaker task (usex task).

Comment 2 Rachel Sibley 2019-03-12 14:51:31 UTC

We continue to see this in CKI quite regularly, please consider fixing this:

https://beaker.engineering.redhat.com/jobs/3226637
https://beaker.engineering.redhat.com/jobs/3407031
https://beaker.engineering.redhat.com/jobs/3330375
https://beaker.engineering.redhat.com/jobs/3403714