Bugzilla – Bug 1212668
Wicked infinite loop if both DHCP and fallback IP configured
Last modified: 2024-04-02 13:10:22 UTC
This is for wicked-0.6.73-1.1.x86_64 upgraded 2023-06-21. Years ago a Wicked man page recommended that in /etc/sysconfig/network/ifcfg-$INTERFACE if you have BOOTPROTO='dhcp', in some use cases including mine you can save yourself troubleshooting tangles if you also specify a fallback IP address. Here's one of my interface configurations: (Same symptom on non-bridge interfaces too.) STARTMODE='auto' BOOTPROTO='dhcp' USERCONTROL='no' # IPADDR='192.9.200.203/26' # IPADDR_0='2600:3c01:e000:306::cb/112' LLADDR='52:54:00:09:c8:cb' BRIDGE='yes' BRIDGE_PORTS='en0 vnet0' BRIDGE_STP='off' But after the recent update to Wicked, it syslogs 2 to 4 times/second: wickedd[898]: br0: address 192.9.200.203 covered by a static lease (Nothing about IPv6, which on my net is normally gotten by DHCP, not RFC 4862 auto-configuration.) Commenting out the fallback IPs fixed the problem. The fallback IP has saved me several times from a "visit every machine" scenario, and I would really like to see it usable again. But if that is not possible, at least the responsible Wicked component should not get diarrhea of the log file when a violation is detected.
Wicked still support fallback IP addresses! It looks like it is hitting the same regression as in bsc#1212806 . The fix is in `wicked-0.6.73-2.1.x86_64` so it should work with simply tumbleweed update, sorry for the circumstances. *** This bug has been marked as a duplicate of bug 1212806 ***