RHEL 9 NetworkManager profile changes not persisting

📖 ~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 settings work temporarily but revert after restart or reboot.

Environment & Reproduction

IP, DNS, or route edits disappear and interface returns to old configuration.

Root Cause Analysis

Changes applied to runtime only, wrong profile edited, or conflicting automation.

Quick Triage

Run nmcli connection show and verify which profile is bound to the interface.

Step-by-Step Diagnosis

Use nmcli connection modify on the active profile name, not the device alias.

Solution – Primary Fix

Review journalctl -u NetworkManager for dispatcher scripts or rollback actions.

Solution – Alternative Approaches

Use nmcli connection up or device reapply and verify settings remain after restart.

Verification & Acceptance Criteria

Confirm interface zone remains consistent when profile identifiers change.

Rollback Plan

Ensure connection files under /etc/NetworkManager maintain proper labels.

Prevention & Hardening

Review cloud-init, Ansible, or custom scripts that may overwrite network settings.

Related Errors & Cross-Refs

Treat network profiles as code and enforce desired state with one authoritative tool.

Related tutorial: View the step-by-step tutorial for rhel-9.

View all rhel-9 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Reboot and confirm expected addressing, routes, and DNS are still applied.