Actions
action #92969
closedFailing service os-autoinst-openvswitch after boot of some workers
Start date:
2021-05-23
Due date:
% Done:
0%
Estimated time:
Description
Observation¶
https://stats.openqa-monitor.qa.suse.de/d/KToPYLEWz/failed-systemd-services shows
Currently failing services
Last update | Host | Failing units | # failed services
2021-05-23 05:48:00 | openqaworker-arm-1 | var-lib-openqa-share.mount, os-autoinst-openvswitch | 2
2021-05-23 03:40:00 | openqaworker13 | var-lib-openqa-share.mount | 1
2021-05-23 03:39:00 | grenache-1 | var-lib-openqa-share.mount, os-autoinst-openvswitch | 2
2021-05-22 04:13:00 | openqaworker-arm-2 | var-lib-openqa-share.mount | 1
2021-05-22 01:47:00 | openqaworker-arm-3 | var-lib-openqa-share.mount, os-autoinst-openvswitch | 2
Acceptance criteria¶
- AC1: No failing os-autoinst-openvswitch after multiple reboot of many machines
Suggestions¶
- Read the suggestion how to check reboot stability in https://progress.opensuse.org/projects/openqav3/wiki/Wiki#Best-practices-for-infrastructure-work
- Try to reproduce the problem by rebooting openqaworker-arm-1 or openqaworker-arm-2 in a loop and check if the alert is triggered or pending for long enough so that the alert would trigger
Actions