🟡 Medium   ⏱ 5–30 min  Last verified: 19 May 2026
Affected versions: RHEL 10.0 RHEL 10.1

📖 ~1 min read

Table of contents
  1. Problem Summary
  2. Symptoms
  3. Diagnostics
  4. Root Cause
  5. Primary Fix
  6. Verification
  7. Prevention
  8. Rollback
  9. Automation
  10. Command Reference
  11. Escalation
  12. Related Notes

Problem Summary

dnf update fails while refreshing repository metadata.

Symptoms

Errors include Curl error 28 and repomd.xml timeout messages.

Diagnostics

Run: dnf -v makecache and journalctl -u NetworkManager -b.

Root Cause

DNS latency, proxy misconfiguration, or stale mirrorlist entries.

Primary Fix

Set reliable baseurl, clean cache with dnf clean all, then dnf makecache.

Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Illustrative mockup for rhel-10 — rhel10-b02-p26-1
Illustrative mockup — Progressive Robot — Illustrative mockup — Progressive Robot

Verification

Confirm dnf repolist and successful dnf upgrade transaction.

Illustrative mockup for rhel-10 — rhel10-b02-p26-2
Illustrative mockup — Progressive Robot — Illustrative mockup — Progressive Robot

Prevention

Pin internal mirrors and monitor resolver health.

Rollback

Restore original repo files from /etc/yum.repos.d backup.

Automation

Use a cron health check running dnf -q makecache.

Command Reference

dnf clean all; dnf makecache; dnf repolist -v

Escalation

Collect /var/log/dnf.log and resolver configuration before escalation.

Check firewall egress rules if using firewalld in restrictive environments.

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

View all rhel-10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

Need Expert Help?

If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.