action #25258
closed
[sle][functional][opensuse]test fails in yast2_network_settings, maybe "Set hostname via DHCP" changed default option? -> check needle
Added by okurz over 6 years ago.
Updated over 6 years ago.
Category:
Bugs in existing tests
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
- 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
Interesting, so do you want to take this ticket and monitor it? One passed job should not be enough to convince us.
- Target version set to Milestone 11
Since the last few builds it is still running, imho we can close this?
- Status changed from In Progress to Resolved
- Status changed from Resolved to In Progress
- Due date set to 2017-10-11
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
- Description updated (diff)
Changes not yet in SLE-15.
Waiting for:
- 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.
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
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
- Assignee deleted (
jorauch)
- Status changed from In Progress to Resolved
Also available in: Atom
PDF