On 04/26/2016 03:40 PM, Orion Poplawski wrote:
> On 04/26/2016 11:04 AM, Pat Riehecky wrote:
>> On 04/26/2016 11:56 AM, Orion Poplawski wrote:
>>> On 04/20/2016 08:30 AM, Pat Riehecky wrote:
>>>> On 04/19/2016 12:39 PM, Pat Riehecky wrote:
>>>>> On 04/19/2016 11:00 AM, Orion Poplawski wrote:
>>>>>> On 04/15/2016 08:37 AM, Pat Riehecky wrote:
>>>>>>> I've rebuild the 7 security repos with my workaround in place.
>>>>>>>
>>>>>>> Pat
>>>>>> Seems to have cropped up in sl-fastbugs for SL7 today:
>>>>>>
>>>>>> /etc/cron.daily/0yum-daily.cron:
>>>>>>
>>>>>> Not using downloaded repomd.xml because it is older than what we have:
>>>>>>      Current   : Tue Apr 19 07:54:00 2016
>>>>>>      Downloaded: Tue Apr 19 07:53:59 2016
>>>>>>
>>>>> Crap, Puppet came through and undid my workaround test on the publication
>>>>> setup.
>>>>>
>>>>> I've re-deployed my test workaround and am rebuilding the metadata.
>>>>>
>>>>> Pat
>>>> In theory, everything should behave itself for the security errata push of
>>>> Java 1.8.0 a little later today.
>>>>
>>>> Pat
>>> Appeared again with sl-security:
>>>
>>> # /etc/cron.daily/0yum-daily.cron
>>> Not using downloaded repomd.xml because it is older than what we have:
>>>     Current   : Mon Apr 25 09:59:45 2016
>>>     Downloaded: Mon Apr 25 09:59:42 2016
>>>
>>>
>> That is terribly weird, no security errata went out today.....
>>
>> Pat
> I'll note that the date is yesterday.  Perhaps something comes around and
> reprocesses the repomd.xml file?
>

Ok, I'm pushing the new firefox errata for 7 right now (5 and 6 still 
building).  It has a full complement of attempts to get this sorted out.

Lets see if that does the job.

Pat