|
Bugzilla – Full Text Bug Listing |
| Summary: | wicked fails to set default route using DHCP | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Christian Stoeckl <csto> |
| Component: | Network | Assignee: | wicked maintainers <wicked-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | bwiedemann, kmroz, mt, per |
| Version: | 201408* | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 13.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Christian Stoeckl
2014-08-07 16:00:34 UTC
Possible dup of bnc#890084 which also exhibits things like: Aug 07 11:43:36 linux-1hkq wickedd[615]: Cannot format state into xml for /run/wicked/state-1.xml Please re-test in the following manner and provide all logs: set DEBUG=all in /etc/sysconfig/network/config rm /var/run/wicked/state-* systemctl restart wickedd wicked --debug all ifup all wicked ifstatus all > status.log wicked show-config > configs.log journalctl -b -o short-iso > wicked.log ip addr show > ip_addr.log ip route show > routes.log ip -6 route show >> routes.log Finally, as a workaround for your use (and only after you've gathered the logs above) you might try adding the following to your /etc/sysconfig/network/ifcfg-eno1: DHCLIENT_SET_DEFAULT_ROUTE='yes' Regards, Karol yast2-network were setting DHCLIENT_SET_DEFAULT_ROUTE='no' in ifcfg-XXX This should be fixed in yast2 in the meantime, see also: https://bugzilla.novell.com/show_bug.cgi?id=891045#c59 (In reply to Marius Tomaschewski from comment #2) > yast2-network were setting DHCLIENT_SET_DEFAULT_ROUTE='no' in ifcfg-XXX > > This should be fixed in yast2 in the meantime, see also: > > https://bugzilla.novell.com/show_bug.cgi?id=891045#c59 Have just installed current Factory, no default route was assigned. (In reply to Per Jessen from comment #3) > (In reply to Marius Tomaschewski from comment #2) > > yast2-network were setting DHCLIENT_SET_DEFAULT_ROUTE='no' in ifcfg-XXX > > > > This should be fixed in yast2 in the meantime, see also: > > > > https://bugzilla.novell.com/show_bug.cgi?id=891045#c59 > > Have just installed current Factory, no default route was assigned. Please attach logs as requested in comment 1 as well as a output of: grep ^DHCLIENT_SET_DEFAULT_ROUTE /etc/sysconfig/network/{dhcp,ifcfg-*} (In reply to Marius Tomaschewski from comment #4) > (In reply to Per Jessen from comment #3) > > (In reply to Marius Tomaschewski from comment #2) > > > yast2-network were setting DHCLIENT_SET_DEFAULT_ROUTE='no' in ifcfg-XXX > > > > > > This should be fixed in yast2 in the meantime, see also: > > > > > > https://bugzilla.novell.com/show_bug.cgi?id=891045#c59 > > > > Have just installed current Factory, no default route was assigned. > > Please attach logs as requested in comment 1 as well as a output of: > > grep ^DHCLIENT_SET_DEFAULT_ROUTE /etc/sysconfig/network/{dhcp,ifcfg-*} DHCLIENT_SET_DEFAULT_ROUTE was set to 'no'. I'll try and get the logs later today. (In reply to Per Jessen from comment #5) > (In reply to Marius Tomaschewski from comment #4) > > (In reply to Per Jessen from comment #3) > > > (In reply to Marius Tomaschewski from comment #2) > > > > yast2-network were setting DHCLIENT_SET_DEFAULT_ROUTE='no' in ifcfg-XXX > > > > > > > > This should be fixed in yast2 in the meantime, see also: > > > > > > > > https://bugzilla.novell.com/show_bug.cgi?id=891045#c59 > > > > > > Have just installed current Factory, no default route was assigned. > > > > Please attach logs as requested in comment 1 as well as a output of: > > > > grep ^DHCLIENT_SET_DEFAULT_ROUTE /etc/sysconfig/network/{dhcp,ifcfg-*} > > DHCLIENT_SET_DEFAULT_ROUTE was set to 'no'. I'll try and get the logs later > today. This test system was later installed with the 64bit version, and the initial ifcfg-enp1s1f0 contains: BOOTPROTO='dhcp' STARTMODE='auto' Also, the default route is correctly set. I then started up yast to rename the interface 'eth0', after which the default route was gone, and the new ifcfg-eth0 contains: BOOTPROTO='dhcp' BROADCAST='' DHCLIENT_SET_DEFAULT_ROUTE='no' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' I assume you won't need the logs after this. (In reply to Per Jessen from comment #6) > > DHCLIENT_SET_DEFAULT_ROUTE was set to 'no'. I'll try and get the logs later > > today. > > This test system was later installed with the 64bit version, and the initial > ifcfg-enp1s1f0 contains: > > BOOTPROTO='dhcp' > STARTMODE='auto' > > Also, the default route is correctly set. > > I then started up yast to rename the interface 'eth0', after which the > default route was gone, and the new ifcfg-eth0 contains: > > BOOTPROTO='dhcp' > BROADCAST='' > DHCLIENT_SET_DEFAULT_ROUTE='no' > ETHTOOL_OPTIONS='' > IPADDR='' > MTU='' > NAME='' > NETMASK='' > NETWORK='' > REMOTE_IPADDR='' > STARTMODE='auto' > > I assume you won't need the logs after this. No, I don't need wicked logs as it is not a wicked but a yast2 issue. I'd say, let's open a new bug report or reopen ... bug #895294? But it makes sense to get the yast2 logs -- use save_y2logs to provide them from a system where it happened. I've added a comment to bug 895294 and bug 891045 for now. (In reply to Marius Tomaschewski from comment #8) > But it makes sense to get the yast2 logs -- use save_y2logs to provide them > from a system where it happened. I've added a comment to bug 895294 and bug > 891045 for now. Unfortunately I am not authorised to view either of those. I'll open a new report. (In reply to Per Jessen from comment #9) > (In reply to Marius Tomaschewski from comment #8) > > But it makes sense to get the yast2 logs -- use save_y2logs to provide them > > from a system where it happened. I've added a comment to bug 895294 and bug > > 891045 for now. > > Unfortunately I am not authorised to view either of those. I'll open a new > report. see bug#898114 |