http://bugzilla.opensuse.org/show_bug.cgi?id=916035 Bug ID: 916035 Summary: Wicked bug upgrade fails Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: suse-20050616@bgcomp.co.uk QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Installed wicked-0.6.15-8.1.x86_64 & wicked-service-0.6.15-8.1.x86_64 as part of a bug fix. This fails with the following entry in syslog: ==== 2015-02-02T21:35:44.000000+00:00 eth7 wickedd-nanny[13490]: <buffer>: line 1: End of document while processing element <address> 2015-02-02T21:35:44.000000+00:00 eth7 wickedd-nanny[13490]: Unable to parse policy document <policy name="policy__dummy0" origin="compat:/etc/sysconfig/network/ifcfg-dummy0" uuid="543acf54-416f-0e00-db12-000002000000"> <match> <link-type>dummy</link-type> <device>dummy0</device> </match> <merge> <name>dummy0</name> <control> <mode>boot</mode> <link-detection> <require-link/> </link-detection> </control> <dummy/> <link/> <ipv4> <enabled>true</enabled> <forwarding>true</forwarding> </ipv4> ipv4:static <address> <local>172.16.0.1/24</local> </address> <ipv6> <enabled>true</enabled> <forwarding>true</forwarding> </ipv6> </merge> </policy> <address> A === Everything between the "===" is logged, including the weird 'A' at the end. The contents of /etc/sysconfig/network/ifcfg-dummy0 is: === BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='172.16.0.1/24' MTU='' NAME='' NETMASK='255.255.255.0' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' === None of the /etc/sysconfig/network/ifcfg-* files appear to have been touched and I can only assume that the config files are in a broken state, although that does not mean the interfaces will not come up. This whole wickedd thing appears to have not been either designed, developed or tested properly given the HUGE amount of problems being seen with it. -- You are receiving this mail because: You are on the CC list for the bug.