action #25258
closed[sle][functional][opensuse]test fails in yast2_network_settings, maybe "Set hostname via DHCP" changed default option? -> check needle
0%
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_ui@64bit fails in
yast2_network_settings
because maybe "Set hostname via DHCP" changed default option? -> check needle
Related bug:¶
Related trello card from yast team:¶
Reproducible¶
Fails since (at least) Build 20170822
Expected result¶
Last good: 20170822 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by okurz over 6 years ago
- Subject changed from test fails in yast2_network_settings, maybe "Set hostname via DHCP" changed default option? -> check needle to [sle][functional][opensuse]test fails in yast2_network_settings, maybe "Set hostname via DHCP" changed default option? -> check needle
Updated by jorauch over 6 years ago
In the current version it works, the default is set to "yes: any" again: https://openqa.opensuse.org/tests/486762#step/yast2_network_settings/14
Updated by okurz over 6 years ago
- Assignee set to jorauch
Interesting, so do you want to take this ticket and monitor it? One passed job should not be enough to convince us.
Updated by jorauch over 6 years ago
Since the last few builds it is still running, imho we can close this?
Updated by okurz over 6 years ago
- Status changed from Resolved to In Progress
So it happened again, see https://openqa.opensuse.org/tests/490801#step/yast2_network_settings/15 . Please investigate. I wonder if that is only a test instability or really a flaky product behaviour.
Updated by okurz over 6 years ago
slindomansilla mentions that there are upcoming changes in the current yast sprint, please find the according trello card and update the ticket to feedback then
Updated by okurz over 6 years ago
https://openqa.opensuse.org/tests/493639 is the most recent example. My personal opinion is that I don't care when a new change for yast is expected when a fix should be trivial.
Updated by SLindoMansilla over 6 years ago
- Description updated (diff)
Changes not yet in SLE-15.
Waiting for:
Updated by okurz over 6 years ago
- Priority changed from High to Urgent
then please regard this with urgency regarding Tumbleweed and fix the test based on whatever is the current behavior. Please do not wait for the submissions to be completed. I expect the test can be fixed within 1h and the submissions might take days or weeks to be effective for both SLE15 and Tumbleweed.
Updated by SLindoMansilla over 6 years ago
Also waiting for:
Updated by dimstar over 6 years ago
I think there is a sequence issue here: yast2-network in gui mode checks for dhcp: any; which is/used to be set by yast2-lan in ncurses mode;
Before the split: depending what modules failed between yast2-lan (curses) and yast2_network (gui), the VM was reset to a state before -lan changed the config
Now after the split: yast-lan is in a different test run and never impacts yast2-network -> causing the setting not to be the way y2-network would expect it to be
Updated by dimstar over 6 years ago
dimstar wrote:
I think there is a sequence issue here: yast2-network in gui mode checks for dhcp: any; which is/used to be set by yast2-lan_hostname in ncurses mode;
Before the split: depending what modules failed between yast2-lan_hostname (curses) and yast2_network (gui), the VM was reset to a state before -lan changed the config
Now after the split: yast2-lan_hostname is in a different test run and never impacts yast2-network -> causing the setting not to be the way y2-network would expect it to be
Updated by okurz over 6 years ago
Updated by zluo over 6 years ago
job restarted: https://openqa.opensuse.org/tests/496637
Updated by zluo over 6 years ago
- Status changed from In Progress to Resolved
https://openqa.opensuse.org/tests/496637#step/yast2_network_settings/
it looks good. fixed now