CentOS Stream 9 – Common Problem 114 – 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 ‘No match for argument’ for a known EPEL package.

Environment & Reproduction

epel-release not installed or epel-next not enabled on Stream 9.

Root Cause Analysis

EPEL 9 and EPEL 9 Next split packages between branches.

Quick Triage

dnf repolist enabled | grep -i epel.

Step-by-Step Diagnosis

Check /etc/yum.repos.d/epel*.repo for enabled=1 and correct URL.

Solution – Primary Fix

dnf install epel-release epel-next-release and re-run the install.

Solution – Alternative Approaches

Use copr or build from source SRPM as a last resort.

Verification & Acceptance Criteria

Package installs and dnf info shows EPEL as the source.

Rollback Plan

Disable EPEL repos via dnf config-manager –disable epel*.

Prevention & Hardening

Pin EPEL releasever and mirror locally for stability.

Related Errors & Cross-Refs

Related: GPG key import failures and SCL retirement.

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

EPEL wiki and CentOS Stream FAQ.