📖 ~1 min read
Table of contents
Symptom & Impact
Interfaces flap between managed states and `wicked show` and `nmcli` disagree on ownership.
Environment & Reproduction
Reproduces when both services are enabled, sometimes after a partial migration.
Root Cause Analysis
Two managers claim the same NIC, alternately tearing down and bringing it up.
Quick Triage
Check both: `systemctl is-active wickedd NetworkManager`.
Step-by-Step Diagnosis
Inspect `journalctl -u wickedd -u NetworkManager` for `take over` events.

Solution – Primary Fix
Disable one stack: `systemctl disable –now wicked wickedd` and let NetworkManager own NICs.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Mark specific NICs as unmanaged by NetworkManager in `/etc/NetworkManager/conf.d/`.
Verification & Acceptance Criteria
`nmcli device status` shows expected NICs managed; `wicked show all` reports the rest.
Rollback Plan
Re-enable the legacy stack temporarily if a critical service depended on its scripting hooks.
Prevention & Hardening
Decide one network manager at OS-build time and bake it into the image.
Related Errors & Cross-Refs
Linked to `dhclient` collisions on the same lease.
Related tutorial: View the step-by-step tutorial for sles-16.
View all sles-16 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
SUSE migration guide from wicked to NetworkManager.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.