http://bugzilla.suse.com/show_bug.cgi?id=902771 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mt@suse.com --- Comment #6 from Marius Tomaschewski <mt@suse.com> --- (In reply to kevin vandeventer from comment #5)
systemctl restart wickedd wicked ifup enp9s0 ^^^^^^ all
All config has to be reapplied.
The only text in my /etc/wicked/common.xml is 'false'.
Then the file is broken, please reinstall wicked.
I also have /etc/wicked/nanny.xml but it is blank.
No, do not touch nanny.xml. It is for nanny only. The use-nanny flag is also used in nanny but basically most important in the _client_ which has to feed the config into nanny and not into the wickedd directly.
Should I change false to true in the common.xml file?
It needs this content: <!-- Common configuration file sourced by all application-specific files --> <config> <piddir path="/run/wicked" mode="0755"/> <statedir path="/run/wicked" mode="0755"/> <storedir path="/var/lib/wicked" mode="0755"/> <!-- Config options specific to DBus service --> <dbus> <service name="org.opensuse.Network" /> <schema name="/usr/share/wicked/schema/wicked.xml"/> </dbus> <!-- Use nanny or not: 'false': causes ifup (and ifreload) to apply the config directly into wickedd without nanny involved (one shot setup). 'true': causes ifup (and ifreload) to apply a policy with the effective config to nanny and nanny configures wickedd then; with hotplug support. After a change, restart wickedd.service and execute "wicked ifup all" to (re)apply the config / policies. --> <use-nanny>true</use-nanny> <!-- If you want to make changes to this file, consider putting your changes into /etc/wicked/local.xml instead. Otherwise, you may lose your changes when applying future maintenance updates. --> <include name="local.xml" optional="true" /> </config> -- You are receiving this mail because: You are on the CC list for the bug.