Actions
action #134888
openopenQA Project - coordination #92323: [saga][epic] Scale up: Fine-grained control over use and removal of results, assets, test data
openQA Project - coordination #160302: [epic] Ensure no job results are present in the file system for jobs that are no longer in the database
Ensure no job results are present in the file system for jobs that are no longer in the database - on OSD only
Start date:
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Motivation¶
See #132146-28 and #132146-32. Due to how we synced over content from one VM to another it might happen that there are results directory present that the openQA database considers non-existant hence causing an inconsistency and results that are never cleaned up. I can imagine that this might also happen in other cases so we should come up with an approach to ensure consistency.
Acceptance criteria¶
- AC1: No job results are present in the file system for jobs that are no longer in the database
- AC2: Same as AC1 but also taking the archive directory into account
- AC3: AC1+AC2 are recurringly ensured on openQA instances (at least on demand)
Suggestions¶
- Create a script to do this kind of cleanup and run it once (before running it for real, make sure it would do the right thing by doing a dry-run first)
Updated by okurz about 1 year ago
- Copied from action #132146: Support migration of osd VM to PRG2 - 2023-08-29 size:M added
Updated by okurz 6 months ago
- Subject changed from Ensure no job results are present in the file system for jobs that are no longer in the database to Ensure no job results are present in the file system for jobs that are no longer in the database - on OSD only
- Parent task changed from #123800 to #160302
Actions