action #156733
closed
[security][15-SP6] test fails in clamav
Added by emiler 10 months ago.
Updated 14 days ago.
Category:
Bugs in existing tests
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.
- Description updated (diff)
Perhaps running out of disk space?
- Estimated time set to 8.00 h
- Status changed from New to Workable
- Start date deleted (
2024-03-06)
- Subject changed from [security][SP6] test fails in clamav to [security][15-SP6] test fails in clamav
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.
This started happening in build 59.2. Is it possible we were patching clamav ourselves and stopped patching it for some reason?
- Status changed from Workable to Feedback
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
- Status changed from Feedback to Resolved
ClamAV is not FIPS compliant at the moment. See the bug report for more details.
Closing.
- Status changed from Resolved to Blocked
issue is still present; in my opinion we need to either
- exclude clamav from FIPS testing (until clamav will be FIPS compliant again)
or
- Status changed from Blocked to In Progress
- Assignee changed from emiler to pstivanin
- % Done changed from 0 to 100
- Estimated time changed from 8.00 h to 1.00 h
- Status changed from In Progress to Resolved
Also available in: Atom
PDF