Can DNF treat a total mirror failure as an implicit cache invalidation signal on Rocky Linux?
Rocky Linux repositories rely on DNF's local metadata cache in /var/cache/dnf , governed by the metadata_expire interval. When every mirror in a repository's mirrorlist becomes unreachable, DNF falls back to the next mirror; if all fail, it retains the existing stale cache unless the expiration interval has already elapsed. The core uncertainty is whether a
rockylinux