Reactivation of shipit causing "Connection timed out" OOPSes
Bug #368767 reported by
Ursula Junque
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Critical
|
Francis J. Lacoste | ||
Bug Description
Yesterday, 04/27, we had a lot of:
HTTPFetchingE
and
DiscoveryFailure: Error fetching XRDS document: <urlopen error (110, 'Connection timed out')>
all in the period when shipit was reactivated, between 18h30 and 19h20 UTC approximately. We see that in:
OOPS-1213A1851, OOPS-1213A1875, OOPS-1213B1862, OOPS-1213D2041, OOPS-1213F1746, OOPS-1213F1816.
| Changed in launchpad-foundations: | |
| importance: | Undecided → Critical |
Revision history for this message
| Francis J. Lacoste (flacoste) wrote | #1 |
| Changed in launchpad-foundations: | |
| status: | New → In Progress |
| assignee: | nobody → Francis J. Lacoste (flacoste) |
Revision history for this message
| Francis J. Lacoste (flacoste) wrote | #2 |
| Changed in launchpad-foundations: | |
| milestone: | none → 2.2.4 |
| status: | In Progress → Fix Released |
To post a comment you must log in.
We deployed two instances dedicated to handling login.launchpad