Project

General

Profile

action #115907

[security] test fails in oscap_xccdf_eval_remote

Added by punkioudi 3 months ago. Updated 3 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-08-29
Due date:
% Done:

80%

Estimated time:
Difficulty:
Tags:

Description

Taking a look in a related [bug], this issue does not seem like a product bug, but the test itself needs more RAM resources :)
In stig testsuite the QEMURAM is set to 8192 right now, so we should try and add 16Gb as it is also pointed in the bug comments.
The test fails in x86_64, s390x and aarch64.

Acceptance criteria

  1. Increase the QEMURAM of the stig testsuite and make some VRs to make sure that the test is not out of memory any more
  2. Change the QEMURAM setting in stig testsuite, if all the tests pass fine

Observation

openQA test in scenario sle-15-SP5-Online-aarch64-stig@aarch64 fails in
oscap_xccdf_eval_remote

Test suite description

Maintainer: llzhao@suse.com

Reproducible

Fails since (at least) Build 15.2

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

History

#1 Updated by punkioudi 3 months ago

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

#2 Updated by punkioudi 3 months ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 80

It seems that when we increase QEMURAM=16384, the test doesn't run out of memory:
https://openqa.suse.de/tests/9411909#step/oscap_xccdf_eval_remote/37
https://openqa.suse.de/tests/9411910#step/oscap_xccdf_eval_remote/37

Let's wait and see the latest build runs if the tests pass after this change.

#3 Updated by openqa_review 2 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: stig
https://openqa.suse.de/tests/9417497#step/oscap_xccdf_eval_remote/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.

#4 Updated by punkioudi 3 days ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF