Project

General

Profile

Actions

action #49133

closed

[functional][u][sle][security][sle15sp1] test fails in clamav - clamd starting timeout

Added by whdu about 5 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
Start date:
2019-03-13
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

systemctl start clamd.service timeout (90s by default). It is slow to start clamd, but never happened on my local environment.

It only happened on the work of o.s.d. I would like to change systemd settings for a longer timeout value.

Observation

openQA test in scenario sle-15-SP1-Installer-DVD-aarch64-extra_tests_in_textmode@aarch64 fails in
clamav

Test suite description

Maintainer: asmorodskyi,okurz
Mainly console extratest

Reproducible

Fails since (at least) Build 177.1

Expected result

Last good: 175.4 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 2 (0 open2 closed)

Related to openQA Tests - action #46880: [sle][security] clamav module updateResolvedwhdu2019-01-30

Actions
Has duplicate openQA Tests - action #54851: [functional][u] test fails in clamavRejected2019-07-30

Actions
Actions #1

Updated by whdu about 5 years ago

  • Subject changed from test fails in clamav - clamd start timeout to [sle][security][sle15sp1] test fails in clamav - clamd start timeout
Actions #2

Updated by whdu about 5 years ago

  • Related to action #46880: [sle][security] clamav module update added
Actions #3

Updated by whdu about 5 years ago

  • Subject changed from [sle][security][sle15sp1] test fails in clamav - clamd start timeout to [sle][security][sle15sp1] test fails in clamav - clamd starting timeout
Actions #4

Updated by SLindoMansilla over 4 years ago

  • Has duplicate action #54851: [functional][u] test fails in clamav added
Actions #5

Updated by SLindoMansilla over 4 years ago

  • Subject changed from [sle][security][sle15sp1] test fails in clamav - clamd starting timeout to [functional][u][sle][security][sle15sp1] test fails in clamav - clamd starting timeout

Reproducible in functional SLE15-SP2: https://openqa.suse.de/tests/3761162#step/clamav/20
Isn't this a product bug.

Actions #6

Updated by zluo over 4 years ago

  • Status changed from In Progress to Workable

correct status because no assignment

Actions #7

Updated by jorauch over 4 years ago

  • Status changed from Workable to In Progress
  • Assignee set to jorauch

Taking a look

Actions #8

Updated by jorauch about 4 years ago

Lets find out, if this ever worked

Actions #9

Updated by jorauch about 4 years ago

Actions #11

Updated by jorauch about 4 years ago

  • Status changed from In Progress to Feedback

Lets wait a few more builds just to be sure

Actions #12

Updated by jorauch about 4 years ago

  • Status changed from Feedback to Resolved

As we haven't seen it for a long time https://openqa.suse.de/tests/3852928#next_previous I am closing this

Actions #13

Updated by SLindoMansilla about 4 years ago

  • Target version set to Milestone 30
Actions #14

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: extra_tests_in_textmode
https://openqa.suse.de/tests/4024327

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 #15

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: extra_tests_in_textmode
https://openqa.suse.de/tests/4024327

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

Also available in: Atom PDF