action #41429
closed[functional][y] test fails in yast2_network_setup - another case related to NM is the default network management
0%
Description
Updated by okurz over 5 years ago
- Subject changed from test fails in yast2_network_setup - another case related to NM is the default network management to [functional][y] test fails in yast2_network_setup - another case related to NM is the default network management
- Due date set to 2018-10-23
- Status changed from New to Workable
- Target version set to Milestone 20
I assume we should adapt the test module to accept the notice that NetworkManager is active and execute the subset of tests from the module that make sense in this scenario. Or: Whenever we detect this dialog we switch to wicked and then execute the normal path.
@mlin7442 we can ask the team QSF-y for help but we are straining their nerves and ressources when we ask them to fix what someone else broke. In my opinion I would not have ignored this test failure for a release of Tumbleweed but would have reverted the submission for the change to NetworkManager after we found all failing tests, let the tests be fixed in a careful way and then resubmit the change to the product. An alternative of course can always be an extension of the staging projects. What do you think?
Updated by okurz over 5 years ago
- Related to action #40049: [functional][y] test fails in yast2_network_setup - need better logging w/o network to create product issue added
Updated by riafarov over 5 years ago
- Related to action #40766: [functional][y] test fails in yast2_network_settings added
Updated by okurz over 5 years ago
- Has duplicate action #41564: [functional][y] test fails in yast2_network_setup added
Updated by dheidler over 5 years ago
- Status changed from Workable to In Progress
Updated by dheidler over 5 years ago
- Due date changed from 2018-10-23 to 2018-10-09
- Target version changed from Milestone 20 to Milestone 19
Updated by dheidler over 5 years ago
- Status changed from In Progress to Resolved