action #161381
Updated by okurz 11 months ago
## Observation Same problem as in #160646 From https://suse.slack.com/archives/C02CANHLANP/p1717381703517509 > (Lili Zhao) Hi, multi machine issues found today, for example: https://openqa.suse.de/tests/14504387#step/iscsi_client/8 （ping with packet size 100 failed, problems with MTU size are expected） and https://openqa.suse.de/tests/14504397#step/suseconnect_scc/25 （curl: (7) Couldn't connect to server) possibly related https://suse.slack.com/archives/C02CANHLANP/p1717400281975529 > (Anton Smorodskyi) when I see such error https://openqa.suse.de/tests/14492957#step/prepare_instance/27 No route to host at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/Transaction.pm line 54. I conclude that worker's network is down . Is my assumption correct ? also https://monitor.qa.suse.de/d/nRDab3Jiz/openqa-jobs-test?orgId=1&from=1717347718902&to=1717408634010 shows the significantly higher ratio of multi-machine test failures happening ## Acceptance criteria * **AC1:** The original issue is understood and resolved * **AC2:** The multi-machine backend and/or test failure ratio on https://monitor.qa.suse.de/d/nRDab3Jiz/openqa-jobs-test is back code can point better to sane levels ## Suggestions likely causes of error * Just cover up the symptoms, retrigger jobs as necessary, etc. * Ensure that the **AC3:** The multi-machine test failure ratio on https://monitor.qa.suse.de/d/nRDab3Jiz/openqa-jobs-test is back to sane levels * Add additional ideas as they come up to #161735 ## Out of scope * Fixing the false positive salt-lint #161393 * Ensuring that we check YAML validity of the workerconf #161396 * Fixing and preventing the actual issue **AC4:** Similar future issues are prevented with better CI checks