Auto Package Testing

Kernel panics / testbed failures in scalingstack

Bug #1792903 reported by Dimitri John Ledkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Auto Package Testing
New
Undecided
Unassigned

Bug Description

For example:

http://autopkgtest.ubuntu.com/packages/s/systemd/cosmic/i386

239-7ubuntu7 dbus/1.12.10-1ubuntu2 2018-09-07 01:51:58 UTC 3h 48m 57s jbicha fail log   artifacts   ♻

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/i386/s/systemd/20180906_071512_4d358@/log.gz

Has a kernel panic, and it ends with a testbed failure. Reruns help.

The tell tell sign is 3+/4+ plus runs, failure, test timeout, and kernel panic in the log (ie. grep for "cut here" and "end trace")

other examples

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/i386/s/systemd/20180907_015158_a1636@/log.gz

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/i386/s/systemd/20180904_182744_cf453@/log.gz

I've seen this for small packages too, where a "retry" fixes everything.

Revision history for this message
Iain Lane (laney) wrote :

this sounds like a kernel bug - or do you think there is something for autopkgtest / autopkgtest-cloud to do?

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

The kernel itself is fine on retry or when the cloud is quiet. Thus it requires logs from the nova to check that the host/vm was stable at the time. It feels like an over-commit issue with cloud itself faulting the kernel in the VM.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.