Bugzilla – Bug 1181296
[Build 129.9] Yast2 lan reports an error if we introduce a typo in ifcfg file
Last modified: 2024-06-03 11:24:07 UTC
## Observation Yast2 lan reports an error if we introduce a typo in ifcfg file. To reproduce: sed -i 's/dhcp/dgcp/' /etc/sysconfig/network/ifcfg-eth0 start yast2 lan openQA test in scenario sle-15-SP3-Online-x86_64-yast2_gui@64bit fails in [yast2_lan_typo](http://waaa-amazing.suse.cz/tests/14117/modules/yast2_lan_typo/steps/16) ## Test suite description ## Reproducible Fails since (at least) Build [129.9](http://waaa-amazing.suse.cz/tests/14117) (current job) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](http://waaa-amazing.suse.cz/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=yast2_gui&version=15-SP3)
(In reply to Jonathan Rivrain from comment #0) > ## Observation > > Yast2 lan reports an error if we introduce a typo in ifcfg file. > > To reproduce: > sed -i 's/dhcp/dgcp/' /etc/sysconfig/network/ifcfg-eth0 > start yast2 lan > > openQA test in scenario sle-15-SP3-Online-x86_64-yast2_gui@64bit fails in > [yast2_lan_typo](http://waaa-amazing.suse.cz/tests/14117/modules/ > yast2_lan_typo/steps/16) > > ## Test suite description > > > > ## Reproducible > > Fails since (at least) Build > [129.9](http://waaa-amazing.suse.cz/tests/14117) (current job) > > > ## Expected result > > Last good: (unknown) (or more recent) > > > ## Further details > > Always latest result in this scenario: > [latest](http://waaa-amazing.suse.cz/tests/ > latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=yast2_gui&vers > ion=15-SP3) We probably should report a better error report in these cases and just warn the user about a wrong configuration.
Hi, we added a new test module in which we test several errors in those files, here: http://waaa-amazing.suse.cz/tests/14316#step/yast2_lan_ifcfg_errors/1. Obviously, an infinity of errors could be made in a hand-edited config file. What we could see is that in case of errors introduced in the files there is no warning in the Yast module, except for the one reported here. I don't know how hard it would be to implement some form of validation of the file and some warning like "The file has been modified manually, Yast may behave inconsistently", but I'd suggest something like that.
Related (duplicate?): bug #1225807