Actions
action #81382
closed[y][qe-yast][qe-core] OOM detection flawed
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2020-12-28
Due date:
% Done:
0%
Estimated time:
Difficulty:
Tags:
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio-2G fails in
pcre
The JeOS seems just to be the one exposing the issue, but I doubt it is limited to it.
So far, I figured out this sequence of events:
- clamav module installs, runs, tests clamd. In this module already, clamd seems to run OOM, but it is not detected; test continues
- evolution_prep creates a snapshot/anchor
- journalctl test module vacuums and rotates the log (i.e. OOM messages are no longer in the current journal)
- firewalld test module fails, no OOM reported, as the journal was rotated; lastgood loaded
- tests continue, until ralis - which is another (known) module failure. As we loaded a lastgood state from before journal rotation, we have the OOM marker again in the journal, and it is reported.
- From here on, all subsequent modules fail on OOM marker (It is not clear why the OOM checker even runs on a successful test though - after the rails test, all subsequent tests fail)
Actual issues:
- The issue of OOM should have been detected in the clamav test already; according the journal, OOM was there before the eicar test.
- The OOM of the clamav test should not bleed into the other tests and disrupt them.
- There is special code to add a swap file for clamav in case of JeOS - that seems not to work to the extend expected
Test suite description¶
Same as jeos, plus some more tests.
Reproducible¶
Fails since (at least) Build 20190311
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Actions