action #153769
Updated by okurz 4 months ago
## Motivation
When changing the GRE tunnel configuration (`/etc/wicked/scripts/gre_tunnel_preup.sh`) by changing related [salt states](https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/openqa/openvswitch.sls) or `workerconf.sls` in pillars these changes are not applied automatically unlike worker settings. automatically. This can lead to openQA test failures due to inconsistencies as well as potentially incomplete routing due to STP selections. failures.
## Acceptance criteria
* **AC1:** We are able to change the GRE tunnel configuration on any salt-controlled openQA worker without causing openQA test failures failures.
## Suggestions
* Run `ovs-appctl stp/show` like on all workers to see how it currently routes packages
* In the best case our salt states handle this automatically. It would be possible to simply re-run `/etc/wicked/scripts/gre_tunnel_preup.sh` after it has changed.
* Adding/removing ports will cause a temporary unavailability of the network and thus disrupt tests.
* Stop So we needed to first stop the services, then re-run the script and finally start the services again?
* If necessary again. Or we just reboot the host (not sure how easy this is to trigger from salt states).
* In the worst case we make sure the limitation is properly documented with instructions to follow (e.g. command to reboot all workers).
* So simply try out to rerun /etc/wicked/scripts/gre_tunnel_preup.sh in salt after it has changed and monitor for bad consequences
* Monitor https://monitor.qa.suse.de/d/nRDab3Jiz/openqa-jobs-test?orgId=1&viewPanel=24
* If nothing bad happened then assume we are done, else try to trigger reboots
## Further details
* Checkout #152389#note-63 and subsequent comments for further context.
Back