[mirror-admin] every mirror is showing repomd.xml does not match metalink

[Matt Domsch]

On Fri, Apr 09, 2010 at 07:06:03AM -0500, Matt Domsch wrote:
> On Thu, Apr 8, 2010 at 11:16 PM, Chuck Anderson <cra at wpi.edu> wrote:
> >>sudo yum update
> > Loaded plugins: dellsysidplugin2, presto, refresh-packagekit, security
> > fedora/metalink                                          |  20 kB     00:00
> > fedora                                                   | 4.2 kB     00:00
> > fedora/primary_db                                        |  12 MB     00:04
> > updates/metalink                                         | 3.3 kB     00:00
> > updates                                                  | 4.4 kB     00:00
> > http://mirrors.usc.edu/pub/linux/distributions/fedora/linux/updates/12/x86_64/repodata/repomd.xml:
> > [Errno -1] repomd.xml does not match metalink for updates
> 
> What is in /var/cache/yum/x86_64/12/updates/ ?
> sha256sum repomd.xml
> cat metalink.xml
> 
> and send that to me please.
> 
> You're the second person to report this kind of failure today, on
> updates-released-f12&arch=i386
> but requests for same look OK to me now...

I see the failure mode now.  I'll have to figure out how to fix it.

scenario: f12 update pushed 2010-04-03T05:00:31.359362.  The following
f12 update was pushed 2010-04-09T01:30:03.61679, about 6 days later.
So, when the later update got pushed, MM "forgot" about the earlier
update (because it was more than 2 days "stale"), but the mirrors
hadn't yet picked up the new update, so yum refused to use any of the
mirrors.  And of course, it happened simultaneous with 13-Beta getting
staged to the mirrors so mirrors couldn't pick up the F12 update as
quickly as they normally would.

This hadn't bitten us before, when we had a max 7 days stale rule,
because we have been pushing updates faster than every 7 days.  But
with the 2-day rule, we get bit.

-Matt

--