| Summary: |
Wicked infinite loop if both DHCP and fallback IP configured |
| Product: |
[openSUSE] openSUSE Tumbleweed
|
Reporter: |
James Carter <jimc> |
| Component: |
Network | Assignee: |
wicked maintainers <wicked-maintainers> |
| Status: |
RESOLVED
DUPLICATE
|
QA Contact: |
E-mail List <qa-bugs> |
| Severity: |
Normal
|
|
|
| Priority: |
P5 - None
|
CC: |
cfamullaconrad, pdostal
|
| Version: |
Current | |
|
| Target Milestone: |
--- | |
|
| Hardware: |
x86-64 | |
|
| OS: |
openSUSE Tumbleweed | |
|
| Whiteboard: |
|
|
Found By:
|
---
|
Services Priority:
|
|
|---|
|
Business Priority:
|
|
Blocker:
|
---
|
|---|
|
Marketing QA Status:
|
---
|
IT Deployment:
|
---
|
|---|
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.