Ubuntu 22.04 LTS – NetworkManager and netplan renderer mismatch causes interface issues – Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Interfaces flap, routes disappear, or DNS settings oscillate after boot.

Environment & Reproduction

Ubuntu 22.04 desktop/server image with conflicting netplan renderer declarations.

Root Cause Analysis

Both NetworkManager and systemd-networkd attempt to control the same links.

Quick Triage

Inspect netplan YAML renderer values and check active services with systemctl.

Step-by-Step Diagnosis

Confirm which service owns each interface and compare generated backend files.

Solution – Primary Fix

Set one renderer policy in netplan, disable the unused manager, and apply cleanly.

Solution – Alternative Approaches

Segregate interface ownership explicitly if both managers are required for distinct use cases.

Verification & Acceptance Criteria

ip addr and ip route outputs remain stable across reboot and link events.

Rollback Plan

Restore previous netplan file and service enablement state.

Prevention & Hardening

Document renderer standards per host role and enforce in provisioning.

Related Errors & Cross-Refs

DHCP lease conflicts and intermittent DNS issues commonly accompany renderer conflicts.

Related tutorial: View the step-by-step tutorial for Ubuntu 22.04 LTS.

View all Ubuntu 22.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Ubuntu 22.04 netplan renderer and NetworkManager integration docs.