action #175629
Updated by okurz 10 days ago
## Observation
For example
```
diesel.qe.nue2.suse.org:
Minion did not return. [Not connected]
petrol.qe.nue2.suse.org:
Minion did not return. [No response]
```
in https://gitlab.suse.de/openqa/salt-states-openqa/-/jobs/3666125#L433
## Acceptance criteria
* **AC1:** All OSD salt controlled hosts using wireguard consistently bring up wireguard after every boot
## Suggestions
* Identify and fix the problem, maybe systemd service dependency cycle?
* Consider to inform SUSE-IT upstream about the problem
* How about a systemd service override waiting for proper network *before* continuing to bring up wireguard so that we don't care that much about systemd service requirements on "network-online" which is never reliable, see https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ in particular "What does this mean for me, a Developer?". Consider an additional "ExecStart=…" and repeat the existing ExecStart from `systemctl cat wg-quick@.service` with the "…" being some call to wait for proper network before continuing
* Use https://github.com/os-autoinst/scripts/blob/master/reboot-stability-check to ensure stability over reboots of hosts using wireguard, e.g. diesel, petrol, sapworker1
Back