After deployment, there were 18 cases when retries were used:
$ grep -l -a "apt-get failed" /var/lib/jenkins/slave-i-* | wc -l 18
Of them,
$ grep -l -a -E "apt-get failed.+aborting" /var/lib/jenkins/slave-i-* | wc -l 10
still failed at the end.
Final failure errors were like:
W: Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/natty-updates/universe/binary-amd64/Packages 403 Forbidden
I.e. it's the same infamous 403 error we tried to get rid of with S3 mirror.
After deployment, there were 18 cases when retries were used:
$ grep -l -a "apt-get failed" /var/lib/ jenkins/ slave-i- * | wc -l
18
Of them,
$ grep -l -a -E "apt-get failed.+aborting" /var/lib/ jenkins/ slave-i- * | wc -l
10
still failed at the end.
Final failure errors were like:
W: Failed to fetch http:// us-east- 1.ec2.archive. ubuntu. com.s3. amazonaws. com/ubuntu/ dists/natty- updates/ universe/ binary- amd64/Packages 403 Forbidden
I.e. it's the same infamous 403 error we tried to get rid of with S3 mirror.