Project

General

Profile

action #97832

[security][qem][maint][journald_fss] test fails in journald_fss - flaky failures in QEM aggregate tests

Added by vsvecova about 1 year ago. Updated 11 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-09-01
Due date:
% Done:

100%

Estimated time:
8.00 h
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP2-Server-DVD-Updates-s390x-mau-extratests2@s390x-kvm-sle12 fails in
journald_fss

Test suite description

Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Run console tests against aggregated test repo

Reproducible

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

Expected result

Last good: 20210831-2 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues

Has duplicate openQA Tests - action #98508: [security][qem] journald corruption on s390x - journald_fss test fails often on s390xRejected

History

#1 Updated by dzedro about 1 year ago

Closing https://progress.opensuse.org/issues/98508 #98508 as duplicate of this same issue.

#2 Updated by okurz about 1 year ago

  • Has duplicate action #98508: [security][qem] journald corruption on s390x - journald_fss test fails often on s390x added

#3 Updated by tjyrinki_suse about 1 year ago

  • Subject changed from [qem][maint][journald_fss] test fails in journald_fss - flaky failures in QEM aggregate tests to [security][qem][maint][journald_fss] test fails in journald_fss - flaky failures in QEM aggregate tests

journald_fss.pm module mentions it being developed by QE Security, being FIPS/forward secure sealing related.

#4 Updated by openqa_review about 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: mau-extratests2
https://openqa.suse.de/tests/7546447

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#5 Updated by llzhao about 1 year ago

I just wonder will QEM team take this poo and fix it?

#6 Updated by llzhao 11 months ago

  • Assignee set to bchou
  • Estimated time set to 12.00 h

#7 Updated by bchou 11 months ago

  • Status changed from New to In Progress

#8 Updated by bchou 11 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100
  • Estimated time changed from 12.00 h to 8.00 h

The problem should be fixed by removing root-console as select_serial_terminal about the lost key problem while lower worker performance.

SP2:
https://openqa.suse.de/tests/7956194#step/journald_fss/14

SP3:
https://openqa.suse.de/tests/7964000#step/journald_fss/14

SP4:
https://openqa.suse.de/tests/7956582#step/journald_fss/14

We can close this one now and reopen it if necessary.

Also available in: Atom PDF