Bug 1181296 - [Build 129.9] Yast2 lan reports an error if we introduce a typo in ifcfg file
Summary: [Build 129.9] Yast2 lan reports an error if we introduce a typo in ifcfg file
Status: CONFIRMED
Alias: None
Product: PUBLIC SUSE Linux Enterprise Server 15 SP3
Classification: SUSE Linux Enterprise Server
Component: YaST2 (show other bugs)
Version: Snapshot 6
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: unspecified
Assignee: YaST Team
QA Contact: Jiri Srain
URL: http://waaa-amazing.suse.cz/tests/141...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-22 15:08 UTC by Jonathan Rivrain
Modified: 2024-06-03 11:24 UTC (History)
2 users (show)

See Also:
Found By: openQA
Services Priority:
Business Priority:
Blocker: Yes
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Rivrain 2021-01-22 15:08:08 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)
Comment 1 Knut Alejandro Anderssen González 2021-01-25 11:21:18 UTC
(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.
Comment 3 Jonathan Rivrain 2021-01-27 16:44:59 UTC
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.
Comment 4 Stefan Hundhammer 2024-06-03 11:24:07 UTC
Related (duplicate?): bug #1225807