action #137756
Updated by okurz about 1 year ago
## Observation See also #135407#note-34 for the original context. However that ticket doesn't provide so much of an explanation as it indicates what isn't the issue. ## Acceptance criteria * **AC1:** Worker31 Worker32 is known to successfully execute multi-machine jobs ## Suggestions - Inspect [failures in test jobs](https://openqa.suse.de/tests/overview?result=failed&arch=&flavor=&machine=&test=&modules=&module_re=&version=15-SP5&distri=sle&build=poo135407g) in so-far as [they haven't been deleted yet](https://openqa.suse.de/tests/overview?result=failed&arch=&flavor=&machine=&test=&modules=&module_re=&version=15-SP5&distri=sle&build=poo135407h) - Try and find similarly failing cases elsewhere (so far unsuccessful) - Confirm what 10.0.2.101", "10.0.2.102" and "192.0.0.2 respectively are in the context of the test - maybe this could also be made clearer in the test? - Run [the latest ovs-client test](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Server-DVD-Updates&machine=64bit&test=ovs-client&version=15-SP5) with something like PAUSE_AT=ovs_server and debug the SUT live e.g. `openqa-clone-job --skip-chained-deps --parental-inheritance --within-instance https://openqa.suse.de 124375 14 TEST+=$i WORKER_CLASS=worker31 BUILD=poo###### SKIP_MAINTENANCE_UPDATES=1 _GROUP=0`