Unfortunately the mirrors lag behind the release. What you experienced is the mirror not yet having the content.

Would be nice if we could pre-seed the day before or something.

Well, we shouldn't remove the prior ISO until the new one is populated. We had at least 24 hours with no ISO.

Also, updating getfedora.org should hinge on the mirrors being populated, somehow. Do the other WGs have this issue?

Well, we shouldn't remove the prior ISO until the new one is populated. We had at least 24 hours with no ISO.

We actually don't "remove" the iso, but the link does get updated (which is effectively removing it from the website.

Also, updating getfedora.org should hinge on the mirrors being populated, somehow. Do the other WGs have this issue?

No, no other WGs release content (other than rpm updates) after F25 release day.

Oh? Because the Princeton mirror didn't have the 11/21 ISO either.

Maybe that's a bad mirror?

Oh? Because the Princeton mirror didn't have the 11/21 ISO either.

I see it: http://mirror.math.princeton.edu/pub/alt//atomic/stable/Fedora-Atomic-25-20161121.0/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20161121.0.iso

@maxamillion -- do you have any ideas on how we can "pre-seed" the mirrors with released content before we update the website?

So, I just looked up the datagrepper source, and we could make the website build script add a "end=time.time() - (246060)" to the datagrepper request, and it would always be 24 hours late with updating.

I think what we can do is modify the website build script to do exactly what you say, and also modify the content of the email to warn against the mirror delay. I think that should suffice.

another option here is to slightly change how mirrormanager tracks what mirrors have the 2 week atomic content. Right now it's all tracked as part of one "2WA" module so if any mirror has any 2W content then it passes and will be given out to a user. If we tracked each two week release as a separate module then we could avoid getting links to mirrors that don't have the content yet and initially when no mirrors have the content yet, we would just fall back to dl.fedoraproject.org.

chatted with @puiterwijk and @maxamillion about this today. basically the previous comment solution is too complicated. Looking at other solutions there are two things we can do to improve this:

• delay release email

This is something we can do today. Would require @maxamillion to manually send the email a period of time after release.

• wait on UMDL Mirrormanager work

I've been told by patrick that this work will cause our delay to only be a few hours vs the worst case 26 hours that it is today. Until this work is complete we can "ping @puiterwijk" and tell him to "please run Fedora Other UMDL" whenever we do a release.

Note that when we get the full release automation by @maxamillion (even if it's manually triggered), we can have the system only send the email out after everything's synced out to master mirrors, umdl ran, and pickles are synced out (aka, it's available in mirrorlist).

So the UMDL mirrormanager work is done. and the mirrors get updated a lot faster than they used to. I think we can mostly call this one fixed. We'll re-raise issues as we observe them in the future.