yum Metadata Expired and Repositories Stay Stale

📖 ~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 uses outdated metadata and misses available updates.

Environment & Reproduction

Expected packages are not found or versions look older than mirror content.

Root Cause Analysis

Cache corruption, proxy issues, or misconfigured metadata_expire values.

Quick Triage

Review repo files, proxy settings, and current cache timestamps.

Step-by-Step Diagnosis

Run yum repolist -v, yum clean metadata, ls -l /var/cache/yum, and journalctl for proxy or DNS warnings.

Solution – Primary Fix

Clean all yum caches, rebuild with yum makecache fast, verify network service health and firewalld egress policy.

Solution – Alternative Approaches

yum check-update now shows current package listings.

Verification & Acceptance Criteria

Restore previous repo definitions if custom mirror changes fail.

Rollback Plan

Periodically refresh metadata and validate mirror freshness.

Prevention & Hardening

Use a scheduled yum makecache job with journalctl log checks.

Related Errors & Cross-Refs

Subscription-managed repos can mask stale proxy cache behavior.

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

Escalate for upstream mirror synchronization incidents.