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

e2e flake: "kubectl describe pod not running" and logs not copied #24642

Closed
yujuhong opened this issue Apr 21, 2016 · 2 comments
Closed

e2e flake: "kubectl describe pod not running" and logs not copied #24642

yujuhong opened this issue Apr 21, 2016 · 2 comments
Assignees
@fejta
Labels
area/test area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@yujuhong
Copy link
Contributor

https://console.cloud.google.com/storage/browser/kubernetes-jenkins/pr-logs/pull/24634/kubernetes-pull-build-test-e2e-gce/36503/

[k8s.io] Kubectl client
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:426
  [k8s.io] Kubectl describe
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:426
    should check if kubectl describe prints relevant information for rc and pods [Conformance] [It]
    /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:713

    Apr 21 16:20:59.988: Failed to find 1 Running in Pods Status:   0 Running / 1 Waiting / 0 Succeeded / 0 Failed

    /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:1206
------------------------------

Apr 21 16:20:59.992: INFO: At {2016-04-21 16:19:29 -0700 PDT} - event for redis-master: {replication-controller } SuccessfulCreate: Created pod: redis-master-qvw3c
Apr 21 16:20:59.992: INFO: At {2016-04-21 16:19:29 -0700 PDT} - event for redis-master-qvw3c: {default-scheduler } Scheduled: Successfully assigned redis-master-qvw3c to e2e-gce-builder-3-1-minion-jimy
Apr 21 16:20:59.992: INFO: At {2016-04-21 16:19:30 -0700 PDT} - event for redis-master-qvw3c: {kubelet e2e-gce-builder-3-1-minion-jimy} Pulling: pulling image "redis"

It looks like that pod was stuck at image pulling, since that was the last event. It's kind of a known issue that image pulling could be problematic at times, but the test should still avoid using non-tagged images (#20836).

Also, the logs from the nodes were not copied:

Dumping master and node logs to /var/lib/jenkins/workspace/kubernetes-pull-build-test-e2e-gce/_artifacts
Warning: Permanently added '8.35.199.247' (ECDSA) to the list of known hosts.
ERROR: (gcloud.compute.copy-files) Could not fetch instance:
 - The resource 'projects/kubernetes-jenkins-pull/zones/us-central1-f/instances/https' was not found
ERROR: (gcloud.compute.copy-files) Could not fetch instance:
 - The resource 'projects/kubernetes-jenkins-pull/zones/us-central1-f/instances/https' was not found
ERROR: (gcloud.compute.copy-files) Could not fetch instance:
 - The resource 'projects/kubernetes-jenkins-pull/zones/us-central1-f/instances/https' was not found
ERROR: (gcloud.compute.copy-files) Could not fetch instance:
 - The resource 'projects/kubernetes-jenkins-pull/zones/us-central1-f/instances/https' was not found
ERROR: (gcloud.compute.copy-files) Could not fetch instance:
 - The resource 'projects/kubernetes-jenkins-pull/zones/us-central1-f/instances/https' was not found
ERROR: (gcloud.compute.copy-files) Could not fetch instance:
 - The resource 'projects/kubernetes-jenkins-pull/zones/us-central1-f/instances/https' was not found
@yujuhong yujuhong added area/test area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. labels Apr 21, 2016
This was referenced Apr 21, 2016
Merged
Closed
@yujuhong yujuhong added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Apr 22, 2016
@spxtr
Copy link
Contributor

spxtr commented Apr 25, 2016

https://console.cloud.google.com/storage/kubernetes-jenkins/logs/kubernetes-e2e-gce/15535/

@freehan freehan mentioned this issue Apr 25, 2016
Merged
@fejta fejta self-assigned this Apr 26, 2016
@fejta
Copy link
Contributor

fejta commented Apr 26, 2016 •
edited
Loading

This looks like the flakiest e2e test now, but updating the image is a bit annoying because it is in the guestbook (although it probably shouldn't). I'll find someone to work on this.

@fejta fejta mentioned this issue Apr 27, 2016
Merged
@liangchenye liangchenye mentioned this issue Apr 28, 2016
Merged
@andyzheng0831 andyzheng0831 mentioned this issue Apr 29, 2016
Merged
k8s-github-robot pushed a commit that referenced this issue May 4, 2016
Merge pull request #24849 from fejta/flake
3b63b06 
Automatic merge from submit-queue

Use tagged redis image for kubectl test, move json test file out of deprecated examples

Closes #24642

Changes the redis image to use the :e2e tagged version on gcr.io.

Since the examples/ subdir is deprecated in favor of the new kubernetes/kubernetes.github.io I just copied this file to test-manifests/kubectl like some other files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fejta fejta

Labels
area/test area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@fejta @spxtr @yujuhong