apt/python-apt network error

Registered by Robbie Williamson on 2009-11-06

Improve the code to deal better with overloaded mirrors and show more meaningful error information to the user. This includes adding an overloaded proxy that can simulate the behavior of overloaded servers by refusing connections in various ways (sending 111, 403, 404, 500> errors at random). We got hit by this with bug #446956 in update-manager where it does the right thing (error and restore original state), but the error message is pretty bad and the general behavior needs improving. An lts may increase the load on the servers (two upgrades in parallel, plus the image downloading).

Blueprint information

Status:
Started
Approver:
Robbie Williamson
Priority:
Low
Drafter:
Michael Vogt
Direction:
Approved
Assignee:
Michael Vogt
Definition:
Approved
Series goal:
Accepted for lucid
Implementation:
Good progress
Milestone target:
None
Started by
Michael Vogt on 2010-02-17

Related branches

Sprints

Whiteboard

Work items:
write fault-injecting proxy that can simulate timeouts, data-corruption: DONE
write fault-injecting proxy that can simulate very slow links: TODO
ensure that on old-dist -> new-dist apt does not do list-cleanup if the server returns a error: TODO
ensure that on old-dist -> new-dist on error libapt returns a proper error as well: TODO
ensure that we get proper error message if the server is returning bogus: DONE
test update-manager release-upgrader fetching too: TODO
write regression test for apt based on this: TODO

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.