RHEL 9: dnf Transaction Fails Due to Package Conflicts

📖 ~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 upgrade` or install fails with conflicts between package providers or modular streams.

Environment & Reproduction

Run `dnf check`, `dnf repoquery –duplicates`, and inspect conflicting package names.

Root Cause Analysis

Inspect transaction and module state with `dnf history` and `dnf module list –enabled`.

Quick Triage

Service state is indirect, but verify affected applications before package replacement.

Step-by-Step Diagnosis

Collect transaction details from `journalctl -b | grep -i dnf` and `/var/log/dnf.log`.

Solution – Primary Fix

Use `dnf swap`, reset conflicting module streams, and rerun transaction cleanly.

Solution – Alternative Approaches

Ensure repository access is stable so retries are not misread as dependency issues.

Verification & Acceptance Criteria

SELinux rarely affects package dependency resolution on default policy.

Rollback Plan

Run `dnf check` and a full update dry-run to confirm conflict-free state.

Prevention & Hardening

Avoid mixing unsupported repositories with Red Hat base channels.

Related Errors & Cross-Refs

Revert problematic transaction with `dnf history undo ` when feasible.

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

Review dnf modularity and dependency troubleshooting guidance.