DNF Modular Stream Conflicts in RHEL 9

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

Installing language stacks fails with modular dependency conflicts even though repositories are available.

Environment & Reproduction

Run dnf module list and dnf module info to inspect enabled stream and profile.

Root Cause Analysis

A previously enabled module stream conflicts with required package versions in current AppStream content.

Quick Triage

Run sudo dnf module reset then sudo dnf module enable : and retry installation.

Step-by-Step Diagnosis

Capture the exact modular conflict transaction check output before resetting streams.

Solution – Primary Fix

After reset and enable, dnf resolves dependencies and completes the transaction.

Solution – Alternative Approaches

Confirm with dnf module list that the intended stream is marked [e] enabled.

Verification & Acceptance Criteria

Document approved module streams and avoid ad hoc stream changes on production nodes.

Rollback Plan

If required, reset module again and re-enable the previous known-good stream.

Prevention & Hardening

Use idempotent playbooks to enforce module streams and package sets per environment.

Related Errors & Cross-Refs

Review dnf history info and /var/log/dnf.log for transaction details and dependency failures.

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

Share module list output, enabled streams, and full dnf error text when escalating.