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.

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

[k8s.io] Docker Containers should be able to override the image's default arguments (docker cmd) [Conformance] {Kubernetes e2e suite} #36706

Closed
k8s-github-robot opened this issue Nov 12, 2016 · 3 comments
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/node Categorizes an issue or PR as relevant to SIG Node.
Milestone

Comments

@k8s-github-robot
Copy link

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-release-1.4/2772/

Failed: [k8s.io] Docker Containers should be able to override the image's default arguments (docker cmd) [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/docker_containers.go:43
Expected error:
    <*errors.errorString | 0xc8209425f0>: {
        s: "expected container test-container success: gave up waiting for pod 'client-containers-6a1688d0-a920-11e6-a21b-0242ac11000a' to be 'success or failure' after 5m0s",
    }
    expected container test-container success: gave up waiting for pod 'client-containers-6a1688d0-a920-11e6-a21b-0242ac11000a' to be 'success or failure' after 5m0s
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2283
@k8s-github-robot k8s-github-robot added kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence. labels Nov 12, 2016
@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-multizone/2787/

Failed: [k8s.io] Docker Containers should be able to override the image's default arguments (docker cmd) [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/docker_containers.go:43
Expected error:
    <*errors.errorString | 0xc4206e3380>: {
        s: "failed to get logs from client-containers-68bd25b9-a96e-11e6-96d4-0242ac110003 for test-container: an error on the server (\"unknown\") has prevented the request from succeeding (get pods client-containers-68bd25b9-a96e-11e6-96d4-0242ac110003)",
    }
    failed to get logs from client-containers-68bd25b9-a96e-11e6-96d4-0242ac110003 for test-container: an error on the server ("unknown") has prevented the request from succeeding (get pods client-containers-68bd25b9-a96e-11e6-96d4-0242ac110003)
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2152

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gke-staging/87/

Failed: [k8s.io] Docker Containers should be able to override the image's default arguments (docker cmd) [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/docker_containers.go:43
Expected error:
    <*errors.errorString | 0xc422948da0>: {
        s: "expected pod \"client-containers-98737dbe-bf7f-11e6-9871-0242ac110008\" success: gave up waiting for pod 'client-containers-98737dbe-bf7f-11e6-9871-0242ac110008' to be 'success or failure' after 5m0s",
    }
    expected pod "client-containers-98737dbe-bf7f-11e6-9871-0242ac110008" success: gave up waiting for pod 'client-containers-98737dbe-bf7f-11e6-9871-0242ac110008' to be 'success or failure' after 5m0s
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2167

@dchen1107
Copy link
Member

The same test hasn't failed for a long time on both CVM and COS images, and on both GCE and GKE. The same test on node-e2e hasn't failed for a long time too. Close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Development

No branches or pull requests

4 participants