repo-mirrorlist quality control?

Ralf Corsepius rc040203 at freenet.de
Wed Feb 25 17:58:54 UTC 2015


On 02/25/2015 06:22 PM, Kevin Fenzi wrote:
> On Wed, 25 Feb 2015 17:47:47 +0100
> Ralf Corsepius <rc040203 at freenet.de> wrote:

>> In another (much smaller) project, when pushing updates, we had
>> removed all mirrors from our mirrorlists and had let the server poll
>> "repodata/repomd.xml" from the mirrors to re-adde a mirror to the
>> mirrorlists if this file matched. Of course, this is a primitive
>> heuristic, but it had worked quite well for us.
>
> yeah, sadly we don't have any ability to push to mirrors, they have to
> pull from us.
I sense a misunderstanding. With "pushing" I was referring to 
"uploading/publishing" a package to the repository on the master.
The mirrors were polling ad lib, at intervals at their preference.

I.e. when updating the master repository on the server, we emptied our 
mirrorlists, and let the _master_ poll repomd.xmls from the _mirrors_. 
When it found a mirror's "repomd.xml" was in sync, the mirrors was 
re-add to our mirrorlists on the server.

> The mirrormanager crawler pulls repomd.xml from each
> mirror when it crawls and compares it. However, as noted we can't poll
> all mirrors all the time.
This sounds pretty much like the same approach we had taken.


>>>> It is a provable matter of fact that it points users (yum,
>>>> mock, ...) to broken and out of sync mirrors.
>>>
>>> There will be such times, sure.
>> Here (Germany), in recent times, they happen almost daily. My guess
>> is the "fedora flavors", the launch of f22 and the mass-rebuild on
>> rawhide are showing their nasty side.
>
> So, to be clear you see daily where 'yum update' gives you all mirrors
> erroring out and you cannot get a update list? And 'yum clean all'
> doesn't help?
As I am heavily using mock, I am fairly often seeing this issue with 
mock. With mock w/ rawhide I am even observing hard build-breakdowns 
(Seems to me as if something in f21's mock was changed to not let it use 
mirrors)

> The next time this happens can you file a ticket with the output?
I can try - However, during some periods in recent weeks, these 
incidents were so frequent, I'd not to anything else but filing tickets ;)

Ralf



More information about the devel mailing list