action #89401
closed
[qe-core][clamav] create local mirror for CVD updates auto_review:"console/clamav.pm line 55."
Added by mgrifalconi almost 4 years ago.
Updated over 3 years ago.
Category:
Bugs in existing tests
Target version:
QA - QE-Core: Ready
- Subject changed from test fails in clamav: too many requests to [qe-core][clamav] test fails in clamav: too many requests
- Subject changed from [qe-core][clamav] test fails in clamav: too many requests to [qe-core][clamav] create local mirror for CVD updates
- Description updated (diff)
- Subject changed from [qe-core][clamav] create local mirror for CVD updates to [qe-core][clamav] create local mirror for CVD updates auto_review:"console/clamav.pm line 55."
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
https://openqa.suse.de/tests/5689960
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
- Status changed from New to In Progress
- Assignee set to dzedro
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?
BTW, /usr/bin/cvdupdate
doesn't seem to be owned by any package, where is that from?
o3 assets are not accessible at all, but still the db was cleaned.
cvdupdate is instaled via pip
dzedro wrote:
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.
I thought I could access assets from o3 one week ago, but maybe it was osd.
You are right, I changed it to cvdupdate user. I tested if all affected python packages are instalable, should be good.
dzedro wrote:
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.
Great!
I increased frequency of local mirror update, toi toi toi.
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Didn't see clamav failures due to local mirror lately.
- Target version set to Ready
- Target version changed from Ready to QE-Core: Ready
- Related to action #152827: [tools] cron service updating clamav database failing on OSD + O3 size:S added
Also available in: Atom
PDF