Bug 898114

Summary:	when renaming a network, the config disables the default route from dhcp
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Per Jessen <per>
Component:	YaST2	Assignee:	Martin Vidner <mvidner>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	per
Version:	13.2 Beta 1
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	logs as saved by save_y2logs

Description Per Jessen 2014-09-24 06:59:05 UTC

On a new 13.2 install, the initial network config /etc/sysconfig/network/ifcfg-enp1s1f0 will contain this for instance - 

BOOTPROTO='dhcp'
STARTMODE='auto'

After renaming 'enp1s1f0' to 'eth0' (with yast), the config contains:

BOOTPROTO='dhcp'
BROADCAST=''
DHCLIENT_SET_DEFAULT_ROUTE='no'
ETHTOOL_OPTIONS=''
IPADDR=''
MTU=''
NAME=''
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'

With this config, the default route from dhcp isn't set. See maybe bug#890877 where I first reported this, there are references to two other bugreports, both unfortunately not visible to me.

Comment 1 Arvin Schnell 2014-09-24 07:30:07 UTC

Please provide YaST logs, see http://en.opensuse.org/openSUSE:Bugreport_YaST.

Comment 2 Per Jessen 2014-09-24 07:33:48 UTC

Created attachment 607544 [details]
logs as saved by save_y2logs

Comment 4 Martin Vidner 2014-09-25 09:41:03 UTC

Thanks for the report, Per.

It is fixed in yast2-network-3.1.100 which is in Factory already. (Your test has 3.1.99) Please update and test with that.

This is a duplicate of the SLES12 bug 883836, which you cannot see so I will summarize it here.

The bug was introduced in April while attempting to fix a different problem related to DHCLIENT_SET_DEFAULT_ROUTE: https://github.com/yast/yast-network/pull/189
There we had too many interfaces setting the DR, so we added code to explicitly set DSDR=no in certain cases.

Unfortunately DSDR=no happened in more cases than we had anticipated, resulting in fixes made in https://github.com/yast/yast-network/pull/226 and https://github.com/yast/yast-network/pull/251 .

*** This bug has been marked as a duplicate of bug 883836 ***

Comment 5 Per Jessen 2014-09-27 17:17:51 UTC

(In reply to Martin Vidner from comment #4)
> Thanks for the report, Per.
> 
> It is fixed in yast2-network-3.1.100 which is in Factory already. (Your test
> has 3.1.99) Please update and test with that.

Hi Martin

I tried a 'zypper patch'+'zypper up', but neither one installed anything? 

> This is a duplicate of the SLES12 bug 883836, which you cannot see so I will
> summarize it here.
> 
> The bug was introduced in April while attempting to fix a different problem
> related to DHCLIENT_SET_DEFAULT_ROUTE:
> https://github.com/yast/yast-network/pull/189
> There we had too many interfaces setting the DR, so we added code to
> explicitly set DSDR=no in certain cases.
> 
> Unfortunately DSDR=no happened in more cases than we had anticipated,
> resulting in fixes made in https://github.com/yast/yast-network/pull/226 and
> https://github.com/yast/yast-network/pull/251 .

Thanks for the summary, much appreciated!

Comment 6 Martin Vidner 2014-09-29 09:25:27 UTC

The sources are in OBS: (3.1.101)
https://build.opensuse.org/package/show/openSUSE:Factory/yast2-network
but the package has not been built or published yet: (3.1.99)
http://download.opensuse.org/factory/repo/oss/suse/i586/?P=yast2-network*