CentOS Stream 9 – Common Problem 101 – 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 install fails with ‘module is already enabled’ or conflicting streams.

Environment & Reproduction

Triggered after enabling multiple module streams (e.g. nodejs:18 and :20).

Root Cause Analysis

Modularity allows only one active stream per module per system.

Quick Triage

Run dnf module list –enabled to see active streams.

Step-by-Step Diagnosis

Inspect /etc/dnf/modules.d for stale .module files.

Solution – Primary Fix

Reset the module then enable the desired stream: dnf module reset ; dnf module enable :.

Solution – Alternative Approaches

Disable modularity for the package using AppStream non-module repos when available.

Verification & Acceptance Criteria

dnf module info shows the intended stream as active.

Rollback Plan

Re-enable previous stream and reinstall original RPMs from dnf history.

Prevention & Hardening

Document required module streams in a Kickstart or Ansible role.

Related Errors & Cross-Refs

See also DNF dependency-resolution errors and AppStream metadata bugs.

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

Red Hat docs: ‘Managing software with the DNF tool’ and modularity guide.