Ubuntu 22.04 LTS – NetworkManager shows device unmanaged – 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

NetworkManager cannot control the interface, causing profile application failures.

Environment & Reproduction

Appears when netplan renderer is set to networkd or unmanaged-devices rules are active.

Root Cause Analysis

Ownership conflict between netplan renderer and NetworkManager interface management policy.

Quick Triage

Check current renderer settings and unmanaged device configuration snippets.

Step-by-Step Diagnosis

Trace interface ownership and inspect NetworkManager logs for policy decisions.

Solution – Primary Fix

Set netplan renderer to NetworkManager where appropriate and restart services.

Solution – Alternative Approaches

Keep networkd renderer for servers and manage interfaces with systemd-networkd tooling.

Verification & Acceptance Criteria

Target interface shows managed state and accepts connection profiles normally.

Rollback Plan

Restore prior netplan and NetworkManager config if role-specific networking breaks.

Prevention & Hardening

Standardize renderer selection by host role and avoid mixed ownership models.

Related Errors & Cross-Refs

May coincide with DHCP acquisition failures and interface rename mismatches.

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

NetworkManager and netplan coexistence patterns for Ubuntu 22.04 LTS devices.