[Bug 1155583] New: openQA ppc64le docker test fails "systemd-journald.service: Main process exited, code=dumped, status=6/ABRT"
http://bugzilla.opensuse.org/show_bug.cgi?id=1155583 Bug ID: 1155583 Summary: openQA ppc64le docker test fails "systemd-journald.service: Main process exited, code=dumped, status=6/ABRT" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1071385/modules/dock er/steps/2 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: normand@linux.vnet.ibm.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 822932 --> http://bugzilla.opensuse.org/attachment.cgi?id=822932&action=edit docker-journal.log openQA ppc64le docker test fails "systemd-journald.service: Main process exited, code=dumped, status=6/ABRT" The last occurence is current snapshot 20191030, but also has occurrences on previous ones: https://openqa.opensuse.org/tests/1071385#step/docker/2 <= 20191030 https://openqa.opensuse.org/tests/1060534#step/docker/2 <= 20191018, idem https://openqa.opensuse.org/tests/1057844#step/docker/2 <= 20191014, idem extract of attached journalctl log: === Oct 31 09:45:19 susetest systemd[1]: systemd-journald.service: Main process exited, code=dumped, status=6/ABRT Oct 31 09:45:19 susetest systemd[1]: systemd-journald.service: Failed with result 'watchdog'. Oct 31 09:45:19 susetest systemd[1]: systemd-journald.service: Service has no hold-off time (RestartSec=0), scheduling restart. Oct 31 09:45:19 susetest systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 2. Oct 31 09:45:19 susetest systemd[1]: Stopping Flush Journal to Persistent Storage... Oct 31 09:45:19 susetest systemd[1]: systemd-journal-flush.service: Control process exited, code=exited, status=1/FAILURE Oct 31 09:45:19 susetest systemd[1]: systemd-journal-flush.service: Failed with result 'exit-code'. Oct 31 09:45:19 susetest systemd[1]: Stopped Flush Journal to Persistent Storage. Oct 31 09:45:19 susetest systemd[1]: Stopped Journal Service. Oct 31 09:45:19 susetest systemd[1]: Starting Journal Service... === I do not see direct relation of this failure with docker started module. ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-ppc64le-extra_tests_in_textmode@ppc64le fails in [docker](https://openqa.opensuse.org/tests/1071385/modules/docker/steps/2) ## Test suite description Maintainer: okurz@suse.de Mainly console extratest. ## Reproducible Fails since (at least) Build [20180813](https://openqa.opensuse.org/tests/734137) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=ppc64le&distri=opensuse&flavor=DVD&machine=ppc64le&test=extra_tests_in_textmode&version=Tumbleweed) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1155583
http://bugzilla.opensuse.org/show_bug.cgi?id=1155583#c2
--- Comment #2 from Michel Normand
Michel,
can you check the output of "coredumpctl" and see if it contains related core dumps ?
If so can you show the backtrace of journald when it crashed ?
the failure is a transient one, so adding code in related openQA to capture coredumpctl output when required with pending https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8834 I am waiting new occurrence with captured data before to continue on that bug. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com