action #19730
closed
[tools][openqa-monitoring] "can't remove <needle_path>"
Added by okurz almost 7 years ago.
Updated over 5 years ago.
Category:
Regressions/Crashes
Description
observation¶
[Sun Jun 11 00:06:55 2017] [18666:warn] can't remove aca/f74/accf8d345e53fde33cfa29c697.png
[Sun Jun 11 00:07:15 2017] [18666:warn] can't remove 0ef/30b/59833cda1f620434cff542668e.png
[Sun Jun 11 00:07:22 2017] [18666:warn] can't remove 2b5/8a2/df37edc553a879ee13a23a400c.png
[Sun Jun 11 00:07:22 2017] [18666:warn] can't remove /var/lib/openqa/images/2b5/8a2/.thumbs/df37edc553a879ee13a23a400c.png
[and many more…]
suggestion¶
- check if it is really acceptable behaviour that we can not remove a file (either it's not there or it is there but can not be deleted)
- if acceptable, downgrade warn to debug with better name or ignore after all
workaround¶
monitoring silenced with https://github.com/okurz/openqa_monitoring/commit/e154d937ca91b949508ae4b48e44906aebd75552
- Copied from action #18076: [tools][openqa-monitoring] no products found, retrying version wildcard added
- Description updated (diff)
- Copied to action #19732: [tools][openqa-monitoring] "openqaworker<> wants to grab a new job - killing the old one: …" added
- Target version set to Ready
- Target version changed from Ready to Current Sprint
- Difficulty set to easy
This is acceptable - and as such should be downgraded to debug. We create the database entries for screenshots before they are uploaded, so we don't have uploads and then fail to register them. But this in return can lead to database entries not pointing to real files on upload failures - and we only notice when we cleanup the database (removing old jobs).
- Status changed from New to In Progress
- Status changed from In Progress to Resolved
- Target version changed from Current Sprint to Done
Also available in: Atom
PDF