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] Pods should support retrieving logs from the container over websockets {Kubernetes e2e suite} #30263

Closed
k8s-github-robot opened this issue Aug 9, 2016 · 17 comments
Assignees
Labels
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

@k8s-github-robot
Copy link

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke/12897/

Failed: [k8s.io] Pods should support retrieving logs from the container over websockets {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:129
Aug  8 23:35:16.447: Couldn't delete ns "e2e-tests-pods-fbf0y": an error on the server has prevented the request from succeeding (delete namespaces e2e-tests-pods-fbf0y)
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:245
@k8s-github-robot k8s-github-robot added priority/backlog Higher priority than priority/awaiting-more-evidence. kind/flake Categorizes issue or PR as related to a flaky test. labels Aug 9, 2016
@jsafrane
Copy link
Member

jsafrane commented Aug 9, 2016

another logs:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/30242/node-pull-build-e2e-test/17808/

It's hard to me to see what's wrong there, empty websocket logs look suspicious:

Aug  9 08:01:23.466: INFO: Unexpected websocket logs:

STEP: deleting the pod

@k8s-github-robot
Copy link
Author

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

Failed: [k8s.io] Pods should support retrieving logs from the container over websockets {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:132
Expected error:
    <*errors.StatusError | 0xc820939380>: {
        ErrStatus: {
            TypeMeta: {Kind: "", APIVersion: ""},
            ListMeta: {SelfLink: "", ResourceVersion: ""},
            Status: "Failure",
            Message: "the server does not allow access to the requested resource (get serviceAccounts)",
            Reason: "Forbidden",
            Details: {
                Name: "",
                Group: "",
                Kind: "serviceAccounts",
                Causes: [
                    {
                        Type: "UnexpectedServerResponse",
                        Message: "Forbidden: \"/api/v1/watch/namespaces/e2e-tests-pods-3yise/serviceaccounts?fieldSelector=metadata.name%3Ddefault\"",
                        Field: "",
                    },
                ],
                RetryAfterSeconds: 0,
            },
            Code: 403,
        },
    }
    the server does not allow access to the requested resource (get serviceAccounts)
not to have occurred

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @vishh

This flaky-test issue would love to have more attention...

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @vishh

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/32091/kubernetes-pull-build-test-e2e-gce/57610/

Failed: [k8s.io] Pods should support retrieving logs from the container over websockets {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/pods.go:583
Sep  6 23:47:11.314: Unexpected websocket logs:

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/pods.go:581

Happened on a presubmit run in #32091.

@k8s-github-robot k8s-github-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/backlog Higher priority than priority/awaiting-more-evidence. labels Sep 7, 2016
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @vishh

This flaky-test issue would love to have more attention.

4 similar comments
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @vishh

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @vishh

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @vishh

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @vishh

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @vishh

This flaky-test issue would love to have more attention.

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/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

5 participants