action #67603
Updated by oorlov almost 4 years ago
This issue was found while moving yast2_lan_device_settings test module to YaST Job Group. Though the test module is failing since a lot of builds ago (So, these failures do not relate to the moving of the module, the falures exist in the Functional Job Group as well, but sometimes due to failed modules before the yast2_lan_device_settings it is not executed, so that the failures were not caught).
1. yast2_lan_device_settings is failing constantly on s390x:
2. yast2_lan_device_settings is passing/failing sporadically on
- Passed on svirt-xen-pv : https://openqa.suse.de/tests/4294104#step/yast2_lan_device_settings/67;
- Failed on svirt-xen-pv: https://openqa.suse.de/tests/4296649#step/yast2_lan_device_settings/12;
- Passed on xen-hvm: https://openqa.suse.de/tests/4294118#step/yast2_lan_device_settings/63;
- Failed on xen-hvm: https://openqa.suse.de/tests/4294105#step/yast2_lan_device_settings/24.
As these tests are failing due to unknown reason, it was decided to not include them while moving the test module to YaST Job Group and investigate the failures in the scope of the ticket.
### Acceptance Criteria:
1. The scope of the tests investigated;
2. Failures are fixed if there are problems in the test module; module.
3. yast2_lan_device_settings is added on s390x and xen-pv and xen-hvm machines. OR
4. Bugzilla issue tickets are raised in case there is a product issue.