sstream-mirror traceback on bad image download
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
simplestreams |
New
|
Undecided
|
Unassigned |
Bug Description
I want to use sstream-mirror to mirror the stream and images at cloud-images.
.......
File "/usr/bin/
main()
File "/usr/bin/
tmirror.
File "/usr/lib/
return self.sync_
File "/usr/lib/
self.
File "/usr/lib/
return self.sync_
File "/usr/lib/
self.
File "/usr/lib/
mutable=False, size=data.
File "/usr/lib/
raise checksum_
simplestreams.
The above could happen a number of ways, incomplete download, lost packets during transit, etc. I was able to reproduce the original failures by starting a session of sstream-mirror and then in a separate terminal truncating one of the inprogress files. Truncating the downloading file caused the checksum to fail, and the traceback to occur. The first encounter was just internet weirdness causing a bad image download.
Anyway, the problem here, beyond the traceback which is unhelpful, since we KNOW the issue, is that the whole thing aborts. So, if I am in the process of doing a FULL mirror of multiple arches and releases, I have to start all over again (yes, I realise it will pick up where it left off) rather than sstream-mirror attempting a retry and skipping on failure.
Observed Behaviour: sstream-mirror throws a traceback rather than a handled exception and aborts the entire attempt.
Preferred Behaviour: sstream-mirror, on failure of the sha256sum check retries the failed file 1 or 2 times. on subsequent failure, sstream-mirror outputs a suitable error message and proceeds to the next item.
tags: | added: hwcert-server |