Project

General

Profile

Actions

action #66179

closed

[sle][security][sle15sp3][FIPS]: test fails in "clamav" on aarch64 platform random due to timeout

Added by rfan1 about 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2020-04-29
Due date:
% Done:

100%

Estimated time:
4.00 h
Difficulty:

Description

Observation

systemctl('start clamd', timeout => 400);

The clamd service failed to start within 400s, however,in general, I can pass within 180s.

It might be caused by performance issue, we did some investigation and found that the issue may have sth to do with
https://progress.opensuse.org/issues/53999 (may be caused by many vms running upon single bm at the sametime)

openQA test in scenario sle-15-SP2-Online-aarch64-fips_ker_mode_tests_crypt_tool_textmode_aarch64@aarch64 fails in
clamav

Test suite description

Reproducible

Fails since (at least) Build 176.1

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Record this and will do more investigation later.

Actions #1

Updated by rfan1 about 4 years ago

  • Subject changed from [sle][security][sle15sp2][FIPS]: test gnutls fails in clamav on aarch64 platform random due to timeout to [sle][security][sle15sp2][FIPS]: test fails in "clamav" on aarch64 platform random due to timeout
Actions #2

Updated by okurz about 4 years ago

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

This bug is still referenced in a failing openQA test: fips_env_mode_tests_crypt_tool_textmode_aarch64
https://openqa.suse.de/tests/4246678

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"
  3. The label in the openQA scenario is removed
Actions #3

Updated by rfan1 about 4 years ago

  • % Done changed from 0 to 10

Till now, we hit aarch64 worker down issue for several times, and I am still taking care of this issue without changing any test parameter.

Actions #4

Updated by rfan1 almost 4 years ago

  • Subject changed from [sle][security][sle15sp2][FIPS]: test fails in "clamav" on aarch64 platform random due to timeout to [sle][security][sle15sp3][FIPS]: test fails in "clamav" on aarch64 platform random due to timeout

Move this ticket to SLES15SP3, I will continue check the worker status before modifying the parameter. hopefully we can get the issue fixed with newer OS version (Leap 15.2?)

Actions #5

Updated by rfan1 almost 4 years ago

  • Estimated time set to 4.00 h
Actions #6

Updated by rfan1 over 3 years ago

  • Status changed from New to Workable
  • Priority changed from Normal to Low

Mark it workable since we can increase the timeout as a workaround. however, I still want to monitor the performance issue.

lower the priority for now.

Actions #7

Updated by rfan1 over 3 years ago

  • Status changed from Workable to Resolved
  • % Done changed from 10 to 100

close it for now, since it didn't reproduce in recent builds.

Actions

Also available in: Atom PDF