[qe-core][clamav] create local mirror for CVD updates auto_review:"console/clamav.pm line 55."
We have many clamav tests updating database, it would be faster to use our own local mirror.
I guess it could be setup on osd and ooo.
Fails in multiple SLE versions
openQA test in scenario sle-15-Server-DVD-Updates-x86_64-mau-extratests1@64bit fails in
Fails since (at least) Build 20210303-1
Last good: 20210302-1 (or more recent)
Always latest result in this scenario: latest
Jozef suggests to setup a local mirror to workaround this issue: https://www.clamav.net/documents/private-local-mirrors
#4 Updated by openqa_review about 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: mau-extratests1
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"
- The label in the openQA scenario is removed
#6 Updated by dzedro about 1 year ago
On osd and o3 is cron updating the database every hour.
#7 Updated by favogt about 1 year ago
This breaks all clamav tests on openqa.opensuse.org:
Reading CVD header (main.cld): WARNING: remote_cvdhead: file not found: http://openqa.opensuse.org/assets/repo/cvd/main.cld Reading CVD header (main.cvd): WARNING: remote_cvdhead: file not found: http://openqa.opensuse.org/assets/repo/cvd/main.cvd
Probably caused by asset cleanup?
/usr/bin/cvdupdate doesn't seem to be owned by any package, where is that from?
#9 Updated by favogt about 1 year ago
o3 assets are not accessible at all, but still the db was cleaned.
What do you mean by that?
I had to force a refresh of the database to trigger a redownload, after that it worked fine, at least until the asset cleanup deletes the cvd directory again. This has to be excluded from cleanup to work properly.
cvdupdate is instaled via pip
System wide? If so, that can cause conflicts and will most certainly break on python upgrades.
#12 Updated by favogt about 1 year ago
I thought I could access assets from o3 one week ago, but maybe it was osd.
It's essentially random when asset cleanup deletes the database, it might happen at any point in the future again.
You are right, I changed it to cvdupdate user. I tested if all affected python packages are instalable, should be good.
#17 Updated by dzedro about 1 year ago
I hope after this PR there will be no fail for very long time ...