action #109091
closed[sle][security][backlog] test fails in windows_network_setup "The term 't-DnsClientServerAddress' is not recognized"
Added by okurz about 2 years ago. Updated almost 2 years ago.
100%
Description
Observation¶
openQA test in scenario sle-15-SP4-Online-x86_64-fips_tests_xrdp_remote-desktop-client4@64bit-amd fails in
windows_network_setup
with "The term 't-DnsClientServerAddress' is not recognized". Looks like a mistyped command in powershell.
Reproducible¶
Fails since (at least) Build 117.1 (current job)
Expected result¶
Last good: 116.4 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by bchou about 2 years ago
- Subject changed from [security] test fails in windows_network_setup "The term 't-DnsClientServerAddress' is not recognized" to [sle][security][sle15sp4] test fails in windows_network_setup "The term 't-DnsClientServerAddress' is not recognized"
- Assignee set to bchou
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: fips_tests_xrdp_remote-desktop-client4@64bit-amd
https://openqa.suse.de/tests/8497041#step/windows_network_setup/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.
Updated by bchou about 2 years ago
This is the mistyped error.
The correct term will be "Set-DnsClientServerAddress" .
Previous Passed run https://openqa.suse.de/tests/8559057#step/windows_network_setup/31
I will discuss with Maintainer if there is possible to execute the command slowly.
Updated by llzhao almost 2 years ago
- Subject changed from [sle][security][sle15sp4] test fails in windows_network_setup "The term 't-DnsClientServerAddress' is not recognized" to [sle][security][backlog] test fails in windows_network_setup "The term 't-DnsClientServerAddress' is not recognized"
Updated by bchou almost 2 years ago
Leave some comments on the PR for the latest PR author.
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14200#issuecomment-1123170320
to discuss if the PR can be enhanced.
Updated by rcai almost 2 years ago
this is performance issue.
need try to test how to input the complete command with powershell?
Updated by rcai almost 2 years ago
It's classic type_string issue.
The command is typed too soon because there is no mechanism which is waiting for return value, first letters are lost. I would add wait_still_screen into run_in_powershell fucntion, wait before the command is typed.
Updated by openqa_review almost 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: fips_tests_xrdp_remote-desktop-client4@64bit-amd
https://openqa.suse.de/tests/8765040#step/windows_network_setup/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.
Updated by rfan1 almost 2 years ago
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14200
Good suggestion there:
It's classic type_string issue. The command is typed too soon because there is no mechanism which is waiting for return value, first letters are lost. I would add wait_still_screen into run_in_powershell fucntion, wait before the command is typed.
Updated by rcai almost 2 years ago
Updated by rcai almost 2 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
- Estimated time set to 5.00 h
Updated by rfan1 almost 2 years ago
- Status changed from Resolved to In Progress
- Assignee changed from rcai to rfan1
- % Done changed from 100 to 20
Assign the ticket to me since Roy is on PTO today.
I did check the job history， and found that the test is run on both intel and amd workers.
however, the issue can not be seen on intel setup.
So, we can make sure it is a performance issue.
At the same time, the issue always happened after the approve_network_popup execution. so let me try to add more wait time on this function to see.
sub approve_network_popup {
# if there is the networks popup that ask's if it's ok to be discoverable, approve it
wait_still_screen stilltime => 5, timeout => 10;
assert_screen([qw(networks-popup-be-discoverable no-network-discover-popup)], 60);
if (match_has_tag 'networks-popup-be-discoverable') {
assert_and_click 'network-discover-yes';
wait_screen_change(sub { send_key 'ret' }, 10);
+ wait_still_screen 3
}
}
Updated by rfan1 almost 2 years ago
- % Done changed from 20 to 70
https://openqa.suse.de/tests/8906012 [Case can pass now]
Updated by rfan1 almost 2 years ago
Updated by rfan1 almost 2 years ago
- Status changed from In Progress to Feedback
- % Done changed from 70 to 90
PR merged，
Let me check next openqa result before resolve it.
Updated by rfan1 almost 2 years ago
- Status changed from Feedback to Resolved
- % Done changed from 90 to 100