Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Error: Status 500 trying to pull repository google_containers/kube-registry-proxy: "Internal Error." #21220

Closed
davidopp opened this issue Feb 14, 2016 · 2 comments
Closed

Error: Status 500 trying to pull repository google_containers/kube-registry-proxy: "Internal Error." #21220

davidopp opened this issue Feb 14, 2016 · 2 comments
Assignees
@ixdy
Labels
area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@davidopp
Copy link
Member

I assume this is transient and not worth investigating, but filing an issue as required anyway.

http://kubekins.dls.corp.google.com:8081/job/kubernetes-pull-build-test-e2e-gce/28452/console

+++ [0213 13:58:08] Pulling and writing Docker image for addon: gcr.io/google_containers/pause:2.0
+++ [0213 13:58:08] Pulling and writing Docker image for addon: gcr.io/google_containers/kube-registry-proxy:0.3
Pulling repository gcr.io/google_containers/kube-registry-proxy
2.0: Pulling from google_containers/pause
Digest: sha256:9ce5316f9752b8347484ab0f6778573af15524124d52b93230b9a0dcc987e73e
Status: Image is up to date for gcr.io/google_containers/pause:2.0
Error: Status 500 trying to pull repository google_containers/kube-registry-proxy: "Internal Error."
!!! Error in /var/lib/jenkins/workspace/kubernetes-pull-build-test-e2e-gce/hack/e2e-internal/../../cluster/gce/../../cluster/../build/../build/common.sh:891
  '"${DOCKER[@]}" pull "${addon_path}"' exited with status 1
Call stack:
  1: /var/lib/jenkins/workspace/kubernetes-pull-build-test-e2e-gce/hack/e2e-internal/../../cluster/gce/../../cluster/../build/../build/common.sh:891 kube::release::write_addon_docker_images_for_server(...)
  2: /var/lib/jenkins/workspace/kubernetes-pull-build-test-e2e-gce/hack/e2e-internal/../../cluster/gce/../../cluster/../build/../build/common.sh:775 kube::release::package_server_tarballs(...)
  3: /var/lib/jenkins/workspace/kubernetes-pull-build-test-e2e-gce/hack/e2e-internal/../../cluster/gce/../../cluster/../build/../build/common.sh:705 kube::release::package_tarballs(...)
  4: /var/lib/jenkins/workspace/kubernetes-pull-build-test-e2e-gce/hack/e2e-internal/../../cluster/gce/../../cluster/../build/release.sh:40 main(...)
Exiting with status 1
!!! [0213 13:58:14] unable to pull or write addon image
@davidopp davidopp added priority/backlog Higher priority than priority/awaiting-more-evidence. area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. labels Feb 14, 2016
@davidopp davidopp changed the title rror: Status 500 trying to pull repository google_containers/kube-registry-proxy: "Internal Error." Error: Status 500 trying to pull repository google_containers/kube-registry-proxy: "Internal Error." Feb 14, 2016
@davidopp davidopp mentioned this issue Feb 14, 2016
Merged
@fejta
Copy link
Contributor

fejta commented Feb 17, 2016

Could this be cpu starvation on PR jenkins?
Do we want to retry $DOCKER in common.sh?
Ignore and close out?

@ixdy
Copy link
Member

ixdy commented Feb 17, 2016

The fact that it's Status 500 indicates it was a transient issue with gcr.io. Unless we see this happening more frequently I'm inclined to just ignore and close.

@fejta fejta closed this as completed Feb 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ixdy ixdy

Labels
area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@fejta @ixdy @davidopp