Description of problem: When network connection has not been established and a user runs for example yum update it seems to rerun from cache and does not notify the user that it is doing so.. Version-Release number of selected component (if applicable): -20 How reproducible: Always Steps to Reproduce: 1. Turn off the network interface 2. Run yum update 3. Actual results: Runs from cache without notifying the user that it's doing so why it does. Expected results: User gets notifyed that it's running from cache and does so since it's unable to connect/reach the "repo" "Unable to reach $repo ran from cache" Or some other informative messages that it's doing it and why.. Additional info: Minor nuance..
It operates from a cache if the repomd.xml is within the cache timeout period. It doesn't notify the user b/c at this point it has no reason to. It's not even connected to the network.