> From: Fabian Arrotin > Sent: 07 December 2017 15:17 > > Hi, > > I noticed a small issue on the node generating the mirrorlist, and > that's fixed. Great, it seems to work fine now. > > Some clarification needed though : you have to also understand is that > each repo is tested individually, so while mirror-status can give you an > idea about how "old" or current a mirror is (at the top level), it can > be that mirrorlist will still redirect to that node for /os/ (as it's > validated and doesn't change so is "up2date") while it will not be > included for /updates/ (as it's several days behind what's current) > > Examples : > > curl -4 > 'http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=updates&cc=ch' > => will not list that node > > curl -4 'http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&cc=ch' > => will include that node (as 'os' is still correct and node reachable) > > Let me know if that answers your question Thanks for the clarification, it does make sense. What matters is that the mirror is up to date for the repo being accessed. Best, Diego -- Diego Santa Cruz, PhD Technology Architect spinetix.com