Comment 35 for bug 932088

According to the comments in the bug above we have been able to resolve the 404 Not Found error and HashSum issue by using the following 2 things.
1) sudo sed -i.dist 's,archive.ubuntu.com,archive.ubuntu.com.s3.amazonaws.com,g' /etc/apt/sources.list
2) echo "Acquire::http::Pipeline-Depth 0;" | sudo tee /etc/apt/apt.conf.d/99no-pipelining

I see on ci.linaro.org init for precise instance ami-b5ea34dc has been updated to use all the above.
But, even after applying those changes I still I got the 404 file not found, though not the HashSum mismatch errors this morning continuously.
With this the builds started to be queue in for longer time.
Finally I had to change the ami instance used from beta2 ami-b5ea34dc instance to beta1 ami-2061b349 instance and was able to proceed with the builds.

I believe the mirrors are separately hosted and their availablility are independent of the ec2 instances we use.
In that case how did the error go away when the instance was changed ? Am I missing something.

Also, I see the following http URL in the error slave logs:
W: Failed to fetch http://us-east-1.ec2.us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/precise-updates/universe/binary-i386/Packages 404 Not Found

I guess its malformed, I looked through the sed commands used , they looked fine with me.
sed -i.dist 's,archive.ubuntu.com,us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com,g' /etc/apt/sources.list
sed -i.bk 's,^\(.*://[^.]*.ec2.archive.ubuntu.com\)/,\1.s3.amazonaws.com/,' /etc/apt/sources.list

Any idea on how the above URL appeared ?

These don't appear in the slaves that are booting successfully.