Perform a network sanity check before running the mirror prober
Bug #82647 reported by
Guilherme Salgado
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Kiko suggested that we do a sanity check of our network at the beginning of the mirr-prober script, skipping the actual probe if the sanity check fails.
That way we would avoid sending failure notifications to mirror admins when the problem is on our side.
| Changed in launchpad: | |
| assignee: | nobody → salgado |
| importance: | Undecided → Medium |
| status: | Unconfirmed → Confirmed |
Revision history for this message
| Guilherme Salgado (salgado) wrote | #1 |
Revision history for this message
| Karl Tilbury (karl-tilbury) wrote | #2 |
| Changed in launchpad: | |
| importance: | Medium → Low |
Revision history for this message
| Guilherme Salgado (salgado) wrote Unassign myself from untargetted bugs | #3 |
| Changed in launchpad: | |
| assignee: | salgado → nobody |
| affects: | launchpad-foundations → launchpad-registry |
| tags: | added: mirror |
To post a comment you must log in.
One way of doing this would be to issue a few requests on some host that is known to have a near-100% uptime and only start the actual probing if the requests succeed.