action #137756
closed
Re-enable worker31 for multi-machine tests in production auto_review:"tcpdump.+check.log.+timed out at"
Added by livdywan 7 months ago.
Updated 2 months ago.
Category:
Feature requests
Description
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 is known to successfully execute multi-machine jobs
Suggestions¶
- Inspect failures in test jobs in so-far as they haven't been deleted yet
- 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 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=poo137756 SKIP_MAINTENANCE_UPDATES=1 _GROUP=0
- Copied from action #135407: [tools] Measure to mitigate websockets overload by workers and revert it size:M added
- Project changed from openQA Project to openQA Infrastructure
- Description updated (diff)
- Status changed from New to Blocked
- Assignee set to okurz
- Target version set to Tools - Next
Replaced "worker32" in AC with "worker31"
First waiting for #136013
- Description updated (diff)
- Copied to action #138707: Re-enable worker32 for multi-machine tests in production added
- Target version changed from Tools - Next to future
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: ovs-server
https://openqa.opensuse.org/tests/3749903#step/ovs_server/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: ovs-client
https://openqa.suse.de/tests/13793290#step/ovs_client/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 100 days if nothing changes in this ticket.
- Status changed from Blocked to New
With #136013 having been resolved I guess this isn't blocked and could be estimated once it ends up on the backlog
- Category set to Feature requests
- Status changed from New to Resolved
- Target version changed from future to Ready
Also available in: Atom
PDF