action #173824
Updated by mkittler 9 days ago
## Observation
With #170338 a new service was introduced. qamaster does not currently use wireguard and shouldn't need to use it. But the service configure-source-based-routing@br0.service is still deployed there which might not be necessary nor useful. And it fails. From
`sudo journalctl -e -u configure-source-based-routing@br0.service`
```
Dec 05 13:17:12 qamaster configure-source-based-routing[2192]: Error: ipv4: FIB table does not exist.
Dec 05 13:17:12 qamaster configure-source-based-routing[2192]: Dump terminated
Dec 05 13:17:12 qamaster configure-source-based-routing[2196]: /usr/local/bin/configure-source-based-routing: line 23: jq: command not f>
Dec 05 13:17:12 qamaster systemd[1]: configure-source-based-routing@br0.service: Main process exited, code=exited, status=127/n/a
Dec 05 13:17:12 qamaster systemd[1]: configure-source-based-routing@br0.service: Failed with result 'exit-code'.
Dec 05 13:17:12 qamaster systemd[1]: Failed to start Wicked hook service to configure source based routing for br0.
```
## Suggestions
At least "jq" is missing as dependency. Then there is the error "Error: ipv4: FIB table does not exist." but probably we can extend our salt to not even deploy that on qamaster where it's most likely not needed.
## Rollback actions
* Remove alert from https://monitor.qa.suse.de/alerting/silences `Failed systemd services alert (except openqa.suse.de)`
* Ask Nick about the script if there are questions.