Since around 7:30AM EST (1230PM UTC) the following file has been invalid, resulting in HTTP 404s when trying to pull updateinfo.xml.bz2/primary.xml.gz repo data: https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/6/x86_64/repodata/repomd.xml
My ec2 instances reports a revision of 1541827341, but my desktop machine reports 1541992680.
AWS support was unable to provide any information as I do not own this cloudfront account. They said that if the TTL of any file is long and valid, it may mean that an older copy is served than is available at the origin.
@nirik, @mohanboddu: would this be good to move to the releng repo?
Metadata Update from @bowlofeggs: - Issue priority set to: Waiting on Assignee (was: Needs Review)
smooge from #epel on freenode was able to help get the cache cleared.
No, this is an infrastructure problem, we run that cloudfront instance.
We need to figure out a way to invalidate that file when we update it, but for now it should be fixed.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Confirmed, it is fixed.
Log in to comment on this ticket.