This has been known to help:

% yum clean all
% yum update yum\*
% yum update

On 03/28/2016 04:08 PM, Steven Haigh wrote:
> On 29/03/2016 4:37 AM, Thomas Leavitt wrote:
>> So, I need to qualify swapping chronyd for ntpd as a "resolution"...
>>
>> The problem *mostly* went away. I'm still intermittently getting it, on a smaller set of machines:
>>
>> /etc/cron.daily/0yum-daily.cron:
>>
>> Not using downloaded repomd.xml because it is older than what we have:
>>    Current   : Fri Mar 25 07:54:39 2016
>>    Downloaded: Fri Mar 25 07:54:20 2016
> So I haven't really been following this thread - however, once I read it
> I note that I get this problem at least once an hour from at least one
> of the 30 or so VMs that I have running.
>
> On one of the systems that just threw this error:
> # ntpdate 203.23.237.200
> 29 Mar 07:54:27 ntpdate[15136]: adjust time server 203.23.237.200 offset
> 0.002116 sec
>
> The NTP server at 203.23.237.200 is a stratum 2 public NTP server that I
> run. It syncs from multiple atomic sources provided by the Australian
> Government. It's accurate.
>
> RedHat seems to have something on this - but its locked behind the
> subscription:
>      https://access.redhat.com/solutions/29845
>
> If its only the overnight cron you get it from, it may be good enough to
> modify /etc/sysconfig/yum-autoupdate and add "yum clean all" to PRERUN.
>
> I note that I only ever get these from 7.x systems. 6.x doesn't seem to
> throw this at all.
>


-- 
Miles O'Neal
CAD Systems Engineer
Cirrus Logic | cirrus.com | 1.512.851.4659