Project

General

Profile

action #62864

[qe-core][opensuse][functional] problem_detection relies on coredumpctl being installed, but it is missing in most disk images

Added by dancermak almost 2 years ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
Start date:
2020-01-31
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

I have tried developing a openQA test and saw that the function problem_detection() is invoked after a test failure. In the resulting video I saw that it invokes coredumpctl, however coredumpctl was not installed (at least in the opensuse-Tumbleweed-x86_64-20200129-gnome-x11@64bit.qcow2 disk image).

Should the function try to install it? Or maybe we need to install systemd-coredump by default in the images that use problem_detection().

Tasks

  1. Implement a check in problem_detection() to know if coredumpctl is installed, and if not, install it.

History

#1 Updated by okurz almost 2 years ago

  • Subject changed from problem_detection relies on coredumpctl being installed, but it is missing in most disk images to [opensuse][functional][u] problem_detection relies on coredumpctl being installed, but it is missing in most disk images
  • Category set to Enhancement to existing tests

So we must install the package before any potential applications crash I assume? I suggest you just ensure the necessary packages are installed in one of the test setups but the selection of a good place is not easy. We want to do it as early as possible but not before we updated repos, etc., Also I guess it is way more important for x11 applications as console applications are checked in a more serialized fashion. How about x11_setup maybe? Or maybe take a look in a common test scenario where is the first time we install something with zypper.

#2 Updated by dancermak almost 2 years ago

okurz wrote:

So we must install the package before any potential applications crash I assume? I suggest you just ensure the necessary packages are installed in one of the test setups but the selection of a good place is not easy. We want to do it as early as possible but not before we updated repos, etc., Also I guess it is way more important for x11 applications as console applications are checked in a more serialized fashion. How about x11_setup maybe? Or maybe take a look in a common test scenario where is the first time we install something with zypper.

Or maybe just remove the coredumpctl call? It got added in 2017 and wasn't touched since then, so unless anyone knows whether coredumps are actively looked at, removing it will make problem_detection slightly faster and not impact its current functionality.

#3 Updated by okurz almost 2 years ago

I would prefer to have a working coredump collection. I already missed coredumps often enough but never understood what you found out, simply that coredumpctl isn't there :D

#4 Updated by jorauch over 1 year ago

  • Status changed from New to In Progress
  • Assignee set to jorauch

Taking a look

#5 Updated by jorauch over 1 year ago

I see it like okurz, as QA we should gather as much data as possible

#6 Updated by jorauch over 1 year ago

  • Status changed from In Progress to Workable
  • Assignee deleted (jorauch)

Unassigning due to other more important tasks

#7 Updated by SLindoMansilla over 1 year ago

  • Description updated (diff)
  • Category changed from Enhancement to existing tests to Bugs in existing tests
  • Target version set to Milestone 30
  • Estimated time set to 42.00 h

#8 Updated by tjyrinki_suse about 1 year ago

  • Subject changed from [opensuse][functional][u] problem_detection relies on coredumpctl being installed, but it is missing in most disk images to [qe-core][opensuse][functional] problem_detection relies on coredumpctl being installed, but it is missing in most disk images

#9 Updated by dheidler about 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to dheidler

#10 Updated by dheidler about 1 year ago

  • Status changed from In Progress to Feedback

#12 Updated by dheidler about 1 year ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF