action #170122: [alert][FIRING:1] s390zl13 (s390zl13: partitions usage (%) alert Generic partitions_usage_alert_s390zl13 generic) - openQA Infrastructure - openSUSE Project Management Tool

Actions

Copy link

action #170122

open

[alert][FIRING:1] s390zl13 (s390zl13: partitions usage (%) alert Generic partitions_usage_alert_s390zl13 generic)

Added by okurz about 6 hours ago. Updated about 6 hours ago.

Status:

In Progress

Priority:

Urgent

Assignee:

okurz

Category:

Regressions/Crashes

Target version:

openQA Project - Ready

Start date:

2024-11-21

Due date:

% Done:

Estimated time:

Tags:

infra, s390x, reactive work

Description

Observation¶

https://stats.openqa-monitor.qa.suse.de/d/GDs390zl13/dashboard-for-s390zl13?orgId=1&viewPanel=panel-65090&from=2024-11-20T22:02:59.734Z&to=2024-11-21T07:43:44.179Z&timezone=browser&var-datasource=000000001&refresh=1m

shows two loop devices with 100% usage. This looks like a manual experiment by somebody during hack week. Judging from the timestamp possibly a colleague from APAC timezones.

Actions

Copy link

Updated by okurz about 6 hours ago

Status changed from New to In Progress

Asked rfan in https://suse.slack.com/archives/C02CANHLANP/p1732191529424949

hi, did you mount agama-installer.s390x-10.0.0-openSUSE-Build30.20.iso on s390zl13? We have received a monitoring alert due to 100% usage of those mount points. This obviously does not make sense for the alert to trigger us as an ISO file does not have free space but I just wanted to make you aware and ask if we can offer help

Actions

Copy link

Updated by okurz about 6 hours ago

I unmounted with umount /mnt as the file seems to have been deleted from the source anyway. I wonder if we can prevent the alert on those loop devices with "fstype: iso9660"

Actions

Copy link