action #88621
closed[Timebox:8h] test fails in yast_dns_server
0%
Description
Observation¶
I don't really know the purpose and the expected outcome of the "Dig" command here. That module is maintained by QAM, and it also fails in a similar way for them as seen here https://openqa.suse.de/tests/5466407.
openQA test in scenario sle-15-SP3-Online-x86_64-yast2_cmd@64bit fails in
yast_dns_server
Test suite description¶
QAM team has developed some tests using YaST cmd line, which is less costly to execute and maintain. This test suite is using those test modules for QA SLE functional.
Reproducible¶
Fails since (at least) Build 148.1 (current job)
Expected result¶
Last good: 145.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by JRivrain about 3 years ago
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests) - Status changed from New to Workable
Updated by syrianidou_sofia about 3 years ago
- Status changed from Workable to In Progress
- Assignee set to syrianidou_sofia
Updated by tonyyuan about 3 years ago
It looks like a regex problem in the test. Please try change below:
-$suseip =~ s/.(\d+.\d+.\d+.\d+)./$1/s;
+$suseip =~ s/.\+.\d+.\d+.\d+)$./$1/ms;
Updated by syrianidou_sofia about 3 years ago
tonyyuan wrote:
It looks like a regex problem in the test. Please try change below:
-$suseip =~ s/.(\d+.\d+.\d+.\d+)./$1/s;
+$suseip =~ s/.\+.\d+.\d+.\d+)$./$1/ms;
Thanks for the suggestion, but the failures don't have to do with the regex, which indeed misses first and last character of the ip address, but that is not a problem. From the dig output, the www.suse.com ips seem to belong to different network. I assume it has to do with the openqa workers networking, because I couldn't reproduce this on my local workstation.
Updated by syrianidou_sofia about 3 years ago
www.suse.com was recently containerized, according to one of our IT colleagues. The DNS load balancing seems to be failing-over every 60" to multiple set of IP addresses and due to the frequency of the fail-over, it can occur while the test module yast_dns_server performs the DNS resolution check. It turns out that the failure is reproducible in local workstations, so this doesn't have to do with OSD networking. Changing the domain for the test to one with smaller interval of round robin DNS could be declawing.
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/11991
Updated by syrianidou_sofia about 3 years ago
- Status changed from In Progress to Feedback
Updated by syrianidou_sofia about 3 years ago
- Status changed from Feedback to Resolved
Tests pass on OSD