CentOS Stream 10 – Common Problem 226 – 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

dnf module enable or install aborts and blocks security updates for the affected application stream.

Environment & Reproduction

Triggered after upgrading from older module stream or mixing AppStream and EPEL Modular content.

Root Cause Analysis

Active stream pins packages to a version set incompatible with the requested target stream profile.

Quick Triage

Check enabled streams with dnf module list –enabled and inspect /etc/dnf/modules.d for stale state.

Step-by-Step Diagnosis

Run: sudo dnf module list ; sudo dnf module info :; sudo dnf repoquery –duplicates.

Solution – Primary Fix

Run: sudo dnf module reset -y; sudo dnf module enable : -y; sudo dnf distro-sync -y.

Solution – Alternative Approaches

Pin the desired stream in /etc/dnf/modules.d, or remove EPEL Modular if it shadows AppStream content.

Verification & Acceptance Criteria

dnf module list shows only the intended enabled stream and dnf upgrade completes without conflicts.

Rollback Plan

Restore /etc/dnf/modules.d backup and reinstall the original stream with module reset and enable.

Prevention & Hardening

Document approved module streams per host role and audit changes via dnf history before applying.

Related Errors & Cross-Refs

Often paired with broken dependency errors and conflicting requests during distro-sync.

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

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

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Red Hat AppStream docs and dnf-plugin-modulesync release notes.