action #100907

Increase timeout of the YuiRestClient

Added by JERiveraMoya 4 months ago. Updated 3 months ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:



openQA test in scenario sle-15-SP4-Online-aarch64-select_modules_and_patterns@aarch64 fails in

Right now we use 30 seconds of timeout, which due to the way is developed the client, turned to be 2x30 seconds, 60 seconds (some extra sleep that was used for first iteration of the client).

We should investigate if this extra sleep of 1 second can be removed and consider how to target slower architectures, because more than 30 seconds for an action could be potentially some bug in general, in fact between 10 and 20 seconds developers agree is ok, so 30 seconds is a good number, taking into account that the installer just act as a planner and postpone all the actions to apply the configuration as last step.

For now we agreed to bump timeout to 45 seconds and pospone this development.


#1 Updated by JERiveraMoya 4 months ago

  • Tags set to qe-yast-refinement
  • Project changed from openQA Tests to qe-yast
  • Category deleted (Bugs in existing tests)
  • Target version set to Current

#2 Updated by JERiveraMoya 4 months ago

  • Tags deleted (qe-yast-refinement)
  • Subject changed from Increase timeout of the YuiRestClient and/or target slower architectures to Increase timeout of the YuiRestClient
  • Description updated (diff)
  • Status changed from New to Workable
  • Assignee set to JERiveraMoya
  • Priority changed from Normal to High

#3 Updated by JERiveraMoya 4 months ago

  • Status changed from Workable to Feedback

#4 Updated by JERiveraMoya 3 months ago

  • Status changed from Feedback to Closed

#5 Updated by openqa_review 3 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: select_modules_and_patterns

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Also available in: Atom PDF