action #69610
closedipmi management interface of openqaworker-arm-3 is inaccessible
0%
Description
Reported in https://infra.nue.suse.com/SelfService/Display.html?id=175681
Deleted salt key on osd, paused alerts on https://stats.openqa-monitor.qa.suse.de/alerting/list?state=not_ok. It seems openqaworker-arm-3 is rather unstable and maybe we need to keep the machine out of production if automatic recovery doesn't work. … Unless we want to automatically report tickets to infra when the long-term alert triggers simply by adding a new notification channel in grafana that sends an email to infra@suse.de which automatically creates a ticket? Hm, …
Updated by okurz about 4 years ago
- Copied from action #69034: ipmi management interface of openqaworker-arm-3 is inaccessible added
Updated by okurz about 4 years ago
- Tags changed from arm, ipmi, caching, openQA, sporadic, worker to arm, ipmi, worker
IPMI is back on. I power cycled the machine and it is booting but there was no response in the ticket yet.
Updated by okurz about 4 years ago
- Status changed from Blocked to Resolved
machine and IPMI are back on though there is no response in Infra-ticket. I commented in Infra-ticket about the current status. Added key in salt again and checked that alerts are back.
Updated by okurz about 4 years ago
- Copied to action #70966: ipmi management interface of openqaworker-arm-3 is inaccessible added
Updated by okurz about 4 years ago
- Copied to action #71191: inform EngInfra automatically if the IPMI interfaces are not accessible added