Hello ! As per https://github.com/jenkins-infra/helpdesk/issues/2888#issuecomment-1131453254 and https://status.jenkins.io/issues/2022-05-19-outage-updates/, we suffered from a side effect of this change: the DNS record "updates.jenkins.io" was a CNAME to mirrors.jenkins.io.
As a consequence, requests to updates.jenkins.io were sent to the Kubernetes cluster (instead of the VM serving the service updates.jenkins.io), leading to either HTTPS issues or HTTP/404 errors. We fixed the DNS updates.jenkins.io (back to the VM) around 09:00am UTC but since the TTL was 1 hour, then you might see issues until 10:00am UTC (or until your DNS uncache the record). Sorry for the inconvenience Le jeudi 19 mai 2022 à 11:59:59 UTC+2, FredG a écrit : > Hi, > > Do I assume correctly that this also affects the availability of > ùpdates.jenkins.io`? > I'm having issues connecting to it (e.g. while trying to access the update > center). > > > Regards, > > Fred > > > On Thursday, May 19, 2022 at 9:57:33 AM UTC+2 [email protected] wrote: > >> Hello there! >> >> Reminder that we’re going to change the DNS record of `mirrors.jenkins.io` >> to `get.jenkins.io` in the upcoming hour, enforcing HTTPS. >> >> >> Ref. https://www.jenkins.io/blog/2022/05/13/mirrors/ >> >> >> Cheers, >> >> For the infra team, >> Damien DUPORTAL >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c71953c7-3817-4b1a-9016-15269f18305bn%40googlegroups.com.
