Project

General

Profile

Actions
Copy link

action #107326

closed

command `dig www.opensuse.org +short` fails in yast_dns_server only in aarch64

Added by JERiveraMoya about 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
rainerkoenig
Target version:
Current
Start date:
2022-02-23
Due date:
% Done:

0%

Estimated time:

Description

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

Last good: 43.1 (or more recent)

Acceptance criteria

AC1: Wait enough time for dig command to succeed in this arch.

Suggestions

We could tweak the $wait parameter: http://open.qa/api/testapi/#_script_output

Related issues 1 (0 open — 1 closed)

Related to qe-yam - action #108995: test fails in yast_users- timeoutResolvedrainerkoenig2022-03-25

Actions
Actions
Copy link
 #1

Updated by JERiveraMoya about 2 years ago

  • Project changed from openQA Tests to qe-yam
  • Category deleted (Bugs in existing tests)
  • Status changed from New to Workable
  • Priority changed from Normal to High
  • Target version set to Current
Actions
Copy link
 #2

Updated by rainerkoenig about 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to rainerkoenig
Actions
Copy link
 #3

Updated by rainerkoenig about 2 years ago

Encountered some problems with scripts terminating with SIGTERM. Could be solved by increasing QEMURAM to 4096.

PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14601
MR: https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/merge_requests/401

Also problems in yast_lan were fixed, so now the whole yast2_cmd testsuite works (with the usual soft failures).

Actions
Copy link
 #4

Updated by JERiveraMoya about 2 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #5

Updated by JERiveraMoya about 2 years ago

Actions
Copy link
 #6

Updated by JERiveraMoya about 2 years ago

Apparently it keeps failing, please file a bug (component Other, for example) and consider to decrease the RAM to some reasonable ammount where there are not seen other failures, 2G should be enough or not much more than that.
https://openqa.suse.de/tests/8450355#step/yast_dns_server/16

Actions
Copy link
 #7

Updated by rainerkoenig about 2 years ago

bsc#1197678 reopened.

Actions
Copy link
 #8

Updated by JERiveraMoya about 2 years ago

  • Status changed from Feedback to Blocked

Thanks for reopening, also please answer question about version in https://bugzilla.suse.com/show_bug.cgi?id=1197678#c6 and afteward uncheck the needinfo on you so investigation can keep going by developers.
Once we have a bug in a progress ticket we can set the status to Blocked and continue with other tasks, just replaying when it is needed.
Setting to Blocked.

Actions
Copy link
 #9

Updated by openqa_review about 2 years ago

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

This bug is still referenced in a failing openQA test: yast2_cmd
https://openqa.suse.de/tests/8569798#step/yast_dns_server/1

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

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #10

Updated by JERiveraMoya almost 2 years ago

  • Priority changed from High to Normal

Priority set to Normal. Not working in product validation at the moment. We will tackle later.

Actions
Copy link
 #11

Updated by JERiveraMoya almost 2 years ago

  • Status changed from Blocked to Resolved

Thanks for the investigation.
I think from this point we can just reply to the bug if needed, we don't need this ticket for extra actions.

Actions
Copy link

Also available in: Atom PDF