RHEL 7 yum dependency conflict after enabling mixed repositories

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

yum update fails with package conflicts and required patching cannot proceed. Security remediation is delayed and maintenance windows overrun. Application teams may hold deployments because dependency states are inconsistent.

Environment & Reproduction

Often triggered by combining base, optional, EPEL, and third-party repos without priority controls. Reproduce by enabling overlapping repositories and attempting full yum update on a system with pinned libraries.

Root Cause Analysis

Different repositories provide incompatible versions of the same package set. yum resolver cannot satisfy all constraints simultaneously. Incomplete exclusions and stale packages from prior updates worsen solver behavior.

Quick Triage

List enabled repos, inspect priority and exclude settings, and run yum deplist for conflicting packages. Review journalctl for network or GPG issues so dependency errors are not mixed with transport failures.

Step-by-Step Diagnosis

Identify the exact package chain causing conflict, compare candidate versions by repo, and simulate transactions with disabled repos. Confirm whether conflict is architectural or caused by stale package pins.

Solution – Primary Fix

Set repository priorities, disable conflicting repos for the transaction, clean yum metadata, and run targeted update. Restart impacted daemons using systemctl or service only after package state stabilizes.

Solution – Alternative Approaches

Use satellite channels with curated content views, freeze package baselines per environment, or move specific software into isolated containers. Keep third-party repos disabled by default unless required.

Verification & Acceptance Criteria

yum check and yum update should complete without dependency failures. Required package versions must match approved baseline. Service health and journalctl should show clean restarts after updates.

Rollback Plan

Undo the transaction with yum history rollback where safe, restore previous repo files, and reapply old package versions from local cache or mirror snapshot if necessary.

Prevention & Hardening

Govern repo onboarding, enforce priority/exclude standards, and test updates in staging before production rollout. Keep SELinux enforcing and firewalld policies consistent while performing repository maintenance.

Related Errors & Cross-Refs

Common related errors include Transaction check error and package obsoletes conflicts. Cross-reference GPG trust, mirror consistency, and package pinning strategy in environment-specific runbooks.

Related tutorial: View the step-by-step tutorial for rhel-7.

View all rhel-7 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

See yum.conf, Red Hat package lifecycle notes, and EPEL compatibility guidance. Document approved repository combinations and escalation paths for conflict resolution.