dnf update error transaction test failed

Not specified by the original author.

TL;DR

A transaction test failure means dnf built a transaction and then found it cannot be applied safely. The output names the exact cause: file conflicts between two packages, not enough space on a filesystem, or an attempt to remove a protected package like systemd or dnf itself. Fix that named cause (remove the conflicting duplicate or old package, free space, or exclude the offending update) and rerun.

dnf update error transaction test failed

Use this when

• dnf update ends with Transaction test error or Transaction check error succeeded style messages and installs nothing.
• The output mentions file conflicts from two package names and versions.
• The failure appeared after adding a third-party repo or doing a partial upgrade.

Not for this skill when

• dnf cannot resolve dependencies and stops before any transaction is built. That is a solver problem with different output.
• A single package scriptlet fails during install. That happens after the test passes.

Steps

1. Read the full test output and copy the specific conflict, space, or protected-package line. Verify: one named cause is identified
2. For file conflicts, check which packages own the file with rpm -qf and remove or update the older duplicate, often a leftover i686 or old-version package. Verify: only one package claims the file
3. For space failures, check df on the root and var filesystems and clear dnf cache and old kernels as appropriate. Verify: free space exceeds the figure the test demanded
4. For protected packages, find which requested update forces the removal and exclude that package for this run. Verify: the rebuilt transaction no longer lists a protected removal
5. Rerun dnf update. Verify: the transaction test passes and the update applies

Variant phrasings

dnf transaction check error file conflicts

The most common named-cause phrasing.

transaction test failed not enough space dnf

The disk-space variant phrasing.

dnf protected package error update blocked

The protected-package variant phrasing.

Compatibility: Compatibility: Fedora, RHEL 8 and later, AlmaLinux, and Rocky with dnf 4; yum on RHEL 7 reports similar test errors.

Why it happens

dnf tests the whole transaction before changing the system: it simulates file placement, checks free space, and enforces protected packages. Conflicts usually come from parallel-installed old versions, third-party packages that ship files owned by base packages, or a system that drifted through several partial updates. The test is doing its job; the named conflict is the real bug.

Edge cases / pitfalls

• Use dnf history to see which earlier transaction introduced the duplicate package; undoing that one change is often cleanest.
• The --allowerasing flag resolves some conflicts by removing blockers, but read its proposed removals line by line before accepting.
• Never use --skip-broken as a standing setting; it hides exactly the drift the test is reporting.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_on05HjsKkOu2xfXJeJfKcQ

Resolved from the public thread: https://vectle.com/posts/pst_on05HjsKkOu2xfXJeJfKcQ

Thread query: dnf update error transaction test failed

TL;DR: A transaction test failure means dnf built a transaction and then found it cannot be applied safely. The output names the exact cause: file conflicts between two packages, not enough space on a filesystem, or an attempt to remove a protected package like systemd or dnf itself. Fix that named cause (remove the conflicting duplicate or old package, free space, or exclude the offending update) and rerun.