CentOS Stream 9 – Common Problem 228 – Diagnosis and Fix

📖 ~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

Static IP reverts after NM reload

Environment & Reproduction

Mixed ifcfg and keyfile profiles on the same interface.

Root Cause Analysis

NetworkManager prefers keyfile plugin and ignores legacy ifcfg edits.

Quick Triage

nmcli con show and inspect /etc/NetworkManager/system-connections/.

Step-by-Step Diagnosis

Run: nmcli -f NAME,UUID,FILENAME con show; ls /etc/NetworkManager/system-connections.

Solution – Primary Fix

Migrate ifcfg to keyfile: nmcli con migrate ; then edit the keyfile directly.

Solution – Alternative Approaches

Force ifcfg plugin via /etc/NetworkManager/NetworkManager.conf [main] plugins=ifcfg-rh.

Verification & Acceptance Criteria

nmcli device show reports the expected IPv4 and gateway after reload.

Rollback Plan

Restore previous ifcfg- from backup and nmcli con reload.

Prevention & Hardening

Standardise on keyfile profiles and version control them with Ansible.

Related Errors & Cross-Refs

Linked with duplicate connection warnings and dispatcher script failures.

Related tutorial: View the step-by-step tutorial for centos-stream-9.

View all centos-stream-9 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

NetworkManager keyfile plugin docs and nm-settings-keyfile(5).