Actions
action #120783
closed[Alerting] failed systemd service on worker11, os-autoinst-openvswitch. Failed at system boot, turned ok after some hours size:M
Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
2022-11-20
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Observation¶
Received email "[Alerting] InfluxDB not reachable" at 2022-11-20 03:54. https://stats.openqa-monitor.qa.suse.de/d/KToPYLEWz/failed-systemd-services?from=1668898957390&to=1668947747978&viewPanel=6 shows the alert to go to pending 03:37, that is the time when we apply automatic reboots when necessary, e.g. for kernel and base library changes, and then back to ok 06:38. That's 3h laters. The system journal shows just:
Nov 20 03:37:13 worker11 50mounted-tests[10630]: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro
Nov 20 03:37:13 worker11 sh[2094]: br1 setup-in-progress
Nov 20 03:37:13 worker11 systemd[1]: os-autoinst-openvswitch.service: Control process exited, code=exited, status=162/n/a
Nov 20 03:37:13 worker11 systemd[1]: os-autoinst-openvswitch.service: Failed with result 'exit-code'.
Nov 20 03:37:13 worker11 systemd[1]: Failed to start os-autoinst openvswitch helper.
Acceptance criteria¶
- AC1: os-autoinst-openvswitch is stable after repeated reboots on worker11
Suggestion¶
- In the past there were problematic overrides of the systemd unit present so check for that
Actions