Project

General

Profile

Actions
Copy link

action #156733

open

[security][15-SP6] test fails in clamav

Added by emiler 4 months ago. Updated about 1 month ago.

Status:
Feedback
Priority:
Normal
Assignee:
emiler
Category:
Bugs in existing tests
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
8.00 h
Difficulty:
Tags:
fail

Description

All platforms:

ERROR: Verification: Can't allocate memory
Giving up on http://openqa.oqa.prg2.suse.org/assets/repo/cvd...
ERROR: Update failed for database: daily
ERROR: Database update process failed: Invalid or corrupted CVD/CLD database
ERROR: Update failed.
Actions
Copy link
 #1

Updated by emiler 4 months ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by emiler 4 months ago

Perhaps running out of disk space?

Actions
Copy link
 #3

Updated by tjyrinki_suse 4 months ago

  • Estimated time set to 8.00 h
Actions
Copy link
 #4

Updated by tjyrinki_suse 4 months ago

  • Status changed from New to Workable
  • Start date deleted (2024-03-06)
Actions
Copy link
 #5

Updated by tjyrinki_suse 4 months ago

  • Subject changed from [security][SP6] test fails in clamav to [security][15-SP6] test fails in clamav
Actions
Copy link
 #6

Updated by emiler 3 months ago

  • Assignee set to emiler
Actions
Copy link
 #7

Updated by emiler 3 months ago

MD5 is disabled in FIPS, hence the error, which is caused during file verification.

In this case, the Can't allocate memory error is somewhat of a red herring. The true issue is that when FIPS mode is active, non–FIPS-approved hashing algorithms are disabled, and that includes MD5, which ClamAV uses extensively internally.

Actions
Copy link
 #8

Updated by emiler 3 months ago

This started happening in build 59.2. Is it possible we were patching clamav ourselves and stopped patching it for some reason?

Actions
Copy link
 #9

Updated by emiler 3 months ago · Edited

Possible cause: https://build.suse.de/package/rdiff/SUSE:Factory:Head/clamav?linkrev=base&rev=105
Timestamps are on point. Change happened on 26th, first fail on 28th (first build since).

Actions
Copy link
 #10

Updated by emiler 3 months ago · Edited

  • Status changed from Workable to Feedback
Actions
Copy link
 #11

Updated by openqa_review about 1 month 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
https://openqa.suse.de/tests/14459784#step/git/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