Mirror prober disabled all release mirrors when it shouldn't

Bug #82618 reported by Dmitry Sherman
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Guilherme Salgado

Bug Description

The mirror prober recently sent email notifications to all mirror admins notifying that their mirrors were unreachable and thus were disabled.

This was caused by a bug that'd be present only when running the mirror prober behind an http proxy. We are not able to run the mirror prober again until this is fixed and deployed.

Revision history for this message
Ante Karamatić (ivoks) wrote :

Same here for hr.archive.ubuntu.com.

Revision history for this message
C&W Mirrors (ftp-admin-deactivatedaccount) wrote :

we got one as well for de.releases.ubuntu.com

Stuart Bishop (stub)
Changed in launchpad:
importance: Undecided → Critical
status: Unconfirmed → Confirmed
Changed in launchpad:
assignee: nobody → salgado
Revision history for this message
Guilherme Salgado (salgado) wrote :

We seem to have had a problem with our network that caused the mirror prober to think that all mirrors were unreachable. We're already discussing a way to avoid this in the future (bug 82647).

I apologize for the inconvenience and I'd like to point that we ran the mirror prober again and it finished succesfully, bringing your mirrors back to https://launchpad.net/ubuntu/+cdmirrors.

Revision history for this message
Guilherme Salgado (salgado) wrote :

Please ignore my last comment; it has nothing to do with the bug described here.

description: updated
Changed in launchpad:
status: Confirmed → In Progress
Changed in launchpad:
status: In Progress → Fix Committed
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.