Linaro Android Infrastructure

  1. Bug #932088
  2. Comment #59

Comment 59 for bug 932088

Revision history for this message
Deepti B. Kalakeri (deeptik) wrote :

As suggested in the comment #53 have disabled pipeline in apt, and switched to s3 mirror and I see the following error :

W: Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/precise/main/source/Sources 403 Forbidden

W: Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/precise/universe/source/Sources 403 Forbidden

W: Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/precise/main/binary-amd64/Packages 403 Forbidden

W: Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/precise/universe/binary-amd64/Packages 403 Forbidden

W: Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/precise/main/binary-i386/Packages 403 Forbidden

W: Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/precise/universe/binary-i386/Packages 403 Forbidden

W: Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/precise-updates/main/source/Sources 403 Forbidden

W: Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/precise-updates/universe/source/Sources 403 Forbidden

W: Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/precise-updates/main/binary-amd64/Packages 403 Forbidden

W: Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/precise-updates/universe/binary-amd64/Packages 403 Forbidden

W: Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/precise-updates/main/binary-i386/Packages 403 Forbidden

W: Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/precise-updates/universe/binary-i386/Packages 403 Forbidden

E: Some index files failed to download. They have been ignored, or old ones used instead.

Although the slaves were failing to start up with using us-east-1.ec2.archive.ubuntu.com this morning, they are able to start fine with main archive us-east-1.ec2.archive.ubuntu.com "now".

FYI. am using the ami-3c994355 precise instance to bring up the slaves.
Any other suggestions why this could be happening with the main archive in the morning and as to why it fails now with the s3 mirrors ?