Project

General

Profile

Actions

action #95866

closed

[qe-sap][ha][shap] test fails in check_logs with "segfault detected in the system!" but I failed to find more detailed information about it

Added by okurz over 3 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Enhancement to existing tests
Target version:
-
Start date:
2021-07-22
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP3-SAP-DVD-Updates-x86_64-qam_sles4sap_wmp_hana_node01@64bit-sap-qam fails in
check_logs
with "segfault detected in the system!" but I failed to find more detailed information about it.

The relevant test code is

     if (script_run '(( $(grep -sR segfault /var/log | wc -l) == 0 ))') {
         if (script_run '(( $(egrep -sR iscsiadm.+segfault /var/log | wc -l) == 0 ))') {
             record_soft_failure "bsc#1181052 - segfault on iscsiadm";
         }
         else {
             die "segfault detected in the system! Aborting";
         }
     }

Because I don't see a soft-fail reference to bsc#1181052 I assume that it's not a iscsiadm related segfault. It is not clear if the list from https://openqa.suse.de/tests/6505771#downloads contains log files from /var/log which are meant here.

Test suite description

The base test suite is used for job templates defined in YAML documents. It has no settings of its own.

Reproducible

Fails since (at least) Build 20210721-1 (current job)

Expected result

Last good: 20210720-2 (or more recent)

Also, more details about the segfault should be visible.

Suggestions

  • Please add a useful job template description. The default text is useless here
  • How about instead of piping the grep to wc -l just rely on the exit code of grep itself? E.g. just:
if (script_run 'grep -sR segfault /var/log' == 0) {
         if (script_run 'egrep -sR iscsiadm.+segfault /var/log' == 0) {
             record_soft_failure 'bsc#1181052 - segfault on iscsiadm, see screenshot for details';
         }
         else {
             die 'segfault detected in the system! See screenshot for details. Aborting';
         }
     }

Further details

Always latest result in this scenario: latest

Actions #1

Updated by okurz over 3 years ago

This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . Please consider picking up this ticket within the next 30 days or just set the ticket to the next lower priority of "Normal" (SLO: updated within 365 days). This update was done as agreed within the SUSE QE Sync call 2021-09-01

Actions #2

Updated by okurz over 3 years ago

  • Subject changed from [ha][shap] test fails in check_logs with "segfault detected in the system!" but I failed to find more detailed information about it to [qe-sap][ha][shap] test fails in check_logs with "segfault detected in the system!" but I failed to find more detailed information about it

Using keyword "qe-sap" as verified by jmichel in weekly QE sync 2021-09-15

Actions #3

Updated by jctmichel about 3 years ago

Ticket #95866 appears to be resolved (see: https://bugzilla.suse.com/show_bug.cgi?id=1181052)
and the test is green.

Do you want the "soft-fail" script removed ?

Actions #4

Updated by okurz almost 3 years ago

jctmichel wrote:

Ticket #95866 appears to be resolved (see: https://bugzilla.suse.com/show_bug.cgi?id=1181052)
and the test is green.

oh, are you talking to me? #95866 is the current ticket. You state that it's "resolved" but the ticket is in "New". Do you propose to set it to "Resolved"?

Do you want the "soft-fail" script removed ?

Well, the bug is only RESOLVED, not VERIFIED. So I suggest someone actually verifies the bugfix. Then the softfail reference in os-autoinst-distri-opensuse should be removed or replaced with a die message to fail the test in case the same error condition is met again.

This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives. Please consider picking up this ticket within the next 30 days or just set the ticket to the next lower priority of "Normal" (SLO: updated within 365 days).

Actions #5

Updated by szarate over 2 years ago

These tickets are not on high prio

Actions #6

Updated by szarate over 2 years ago

  • Tags set to bulkupdate

These tickets are not on high pro

Actions #7

Updated by szarate over 2 years ago

  • Priority changed from High to Normal
Actions #8

Updated by rbranco over 2 years ago

  • Status changed from New to Rejected

Closing as expired/non-issue.

Actions

Also available in: Atom PDF