action #28639
Updated by riafarov about 3 years ago
This test scenario occurred in the customer setup, see https://bugzilla.suse.com/show_bug.cgi?id=1061306 YaST must not break if it finds something unexpected in network configuration files (ifcfg). The fact is, that if anything changes in the future, we need to be ready. Customers can add some values either by a mistake or even intentionally, for instance, if they want/need it for some reason (that might be unknown to us). Scope is 64bit only. We can add this scenario to yast2_gui test suite. Test scenario should include at least following steps: 1. Put misconfigured settings in ifcfg file e.g. ETHERDEVICE setting which is expected to be used for VLANs only: ETHERDEVICE='eth0' 2. Run lan module of the yast nd verify it doesn't crash Tasks 1. Implement automated test (4-6h) 2. Add to the SLE Functional job group Acceptance criteria: 1. Automated test runs in production and verifies that lan yast module doesn't crash when ifcfg file contains invalid configuration