Project

General

Profile

Actions
Copy link

action #57689

closed

asset cleanup jobs do not run on o3 (results cleanup works), workaround: unlock locks manually

Added by okurz about 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
okurz
Category:
Regressions/Crashes
Target version:
Ready
Start date:
2019-10-03
Due date:
2019-12-10
% Done:

0%

Estimated time:

Description

Observation

I am receiving monitoring alerts for o3 for usage of /space . https://thruk.suse.de/thruk/cgi-bin/extinfo.cgi?type=2&host=ariel-opensuse.suse.de&service=space%20partition#pnp_th2/1568826977/1568916977/0 shows the details. This happened on 2019-10-03 for the third time. I monitored the space usage and saw that /space was nearly depleted (100 GB free space left).

On
https://openqa.opensuse.org/minion/jobs?state=inactive I see "limit_assets". https://openqa.opensuse.org/minion/jobs?state=finished&offset=0&task=limit_assets do not show any successfully finished "limit_assets" jobs, https://openqa.opensuse.org/minion/jobs?state=finished&offset=0&task=limit_results_and_logs is fine though. https://openqa.opensuse.org/minion/jobs?state=failed mentions "limit_assets".

Related issues 1 (0 open — 1 closed)

Related to openQA Infrastructure (public) - action #57683: o3 /space is nearly running out again, assets are not refreshed, not cleaned up (was: too much logs&results)Resolvedokurz2019-10-03

Actions
Actions
Copy link

Also available in: Atom PDF