Project

General

Profile

Actions
Copy link

action #160466

open

[security] oscap tests fail on ppc64le

Added by tjyrinki_suse 6 months ago. Updated 5 months ago.

Status:
Workable
Priority:
Normal
Assignee:
viktors.trubovics
Category:
Bugs in existing tests
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:
Tags:
oscap

Description

Now that our ppc64le workers (using LPAR) are back, the oscap tests fail to run on those:

15-SP5:
https://openqa.suse.de/tests/14069416/modules/oscap_xccdf_remediate/steps/1
^ this one boots but fails later
https://openqa.suse.de/tests/14069418#step/boot_to_desktop/5
^ this and others fail to boot

The boot issues may be something common with other failures, but the xccdf_remediate might be something else.

15-SP6:
https://openqa.suse.de/tests/14305423

I'm not sure why the first oscap tests - oscap_ansible_anssi_bp28_high_hmc - passes past the boot stage but others don't, even though they should be relatively similar.

Notable openscap-hmc is fully passing:
https://openqa.suse.de/tests/14069388 (15-SP5)
https://openqa.suse.de/tests/14305045 (15-SP6)

Test suite description

Testsuite maintained at https://gitlab.suse.de/qe-security/osd-sle15-security.

Reproducible

Fails since (at least) Build 137.7

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #2

Updated by viktors.trubovics 6 months ago

Will add exclusions and expected results for power platform (for now copy of s390x).
Waiting power vms to be stable and able to boot.

Actions
Copy link
 #3

Updated by tjyrinki_suse 6 months ago

  • Parent task set to #161834
Actions
Copy link
 #4

Updated by openqa_review 5 months ago

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

This bug is still referenced in a failing openQA test: oscap_ansible_cis_hmc
https://openqa.suse.de/tests/14612853#step/boot_to_desktop/1

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

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link

Also available in: Atom PDF