Ubuntu 22.04 LTS – netplan changes do not apply after interface edits – 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

Network configuration updates appear saved but interfaces keep old addresses or routes, causing connectivity and routing drift.

Environment & Reproduction

Occurs after hand-editing YAML indentation, renderer mismatch, or invalid route syntax.

Root Cause Analysis

YAML structure errors, wrong renderer selection, or conflicting files in /etc/netplan prevent generated backend config from loading.

Quick Triage

Run netplan generate with debug output before touching live links.

Step-by-Step Diagnosis

Validate YAML, inspect generated backend config, and compare effective interface state.

Solution – Primary Fix

Fix YAML syntax and renderer, then apply safely with rollback timer if remote.

Solution – Alternative Approaches

Consolidate multiple netplan files into one canonical file to reduce precedence confusion.

Verification & Acceptance Criteria

Interface addresses, routes, and DNS values match intended YAML without packet loss.

Rollback Plan

Restore prior YAML and run netplan apply to return to known-good network state.

Prevention & Hardening

Validate netplan in CI and use templates to avoid manual indentation mistakes.

Related Errors & Cross-Refs

Related to cloud-init generated netplan files and NetworkManager/systemd-networkd renderer mix-ups.

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

Netplan documentation for schema, renderer behavior, and safe remote changes.