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

[k8s.io] Kubectl client [k8s.io] Simple pod should support inline execution and attach {Kubernetes e2e suite} #28845

Closed
k8s-github-robot opened this issue Jul 12, 2016 · 34 comments
Closed

[k8s.io] Kubectl client [k8s.io] Simple pod should support inline execution and attach {Kubernetes e2e suite} #28845

k8s-github-robot opened this issue Jul 12, 2016 · 34 comments
Assignees
@cjcullen
Labels
area/docker kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/cli Categorizes an issue or PR as relevant to SIG CLI.
Milestone
v1.5

Comments

@k8s-github-robot
Copy link

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

Failed: [k8s.io] Kubectl client [k8s.io] Simple pod should support inline execution and attach {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:402
Expected error:
    <*errors.errorString | 0xc82092fe60>: {
        s: "Error running &{/workspace/kubernetes/platforms/linux/amd64/kubectl [kubectl --server=https://104.155.140.207 --kubeconfig=/workspace/.kube/config --namespace=e2e-tests-kubectl-uydhn run run-test --image=gcr.io/google_containers/busybox:1.24 --restart=OnFailure --attach=true --stdin -- sh -c cat && echo 'stdin closed'] []  0xc820872d00  error: failed to discover supported resources: the server could not find the requested resource\n [] <nil> 0xc8208734a0 exit status 1 <nil> true [0xc8200d3658 0xc8200d3680 0xc8200d3690] [0xc8200d3658 0xc8200d3680 0xc8200d3690] [0xc8200d3660 0xc8200d3678 0xc8200d3688] [0xa96460 0xa965c0 0xa965c0] 0xc820d38420}:\nCommand stdout:\n\nstderr:\nerror: failed to discover supported resources: the server could not find the requested resource\n\nerror:\nexit status 1\n",
    }
    Error running &{/workspace/kubernetes/platforms/linux/amd64/kubectl [kubectl --server=https://104.155.140.207 --kubeconfig=/workspace/.kube/config --namespace=e2e-tests-kubectl-uydhn run run-test --image=gcr.io/google_containers/busybox:1.24 --restart=OnFailure --attach=true --stdin -- sh -c cat && echo 'stdin closed'] []  0xc820872d00  error: failed to discover supported resources: the server could not find the requested resource
     [] <nil> 0xc8208734a0 exit status 1 <nil> true [0xc8200d3658 0xc8200d3680 0xc8200d3690] [0xc8200d3658 0xc8200d3680 0xc8200d3690] [0xc8200d3660 0xc8200d3678 0xc8200d3688] [0xa96460 0xa965c0 0xa965c0] 0xc820d38420}:
    Command stdout:

    stderr:
    error: failed to discover supported resources: the server could not find the requested resource

    error:
    exit status 1

not to have occurred

Previous issues for this test: #26324 #27715
@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 Jul 12, 2016
@k8s-github-robot k8s-github-robot mentioned this issue Jul 13, 2016
Closed
@k8s-github-robot k8s-github-robot mentioned this issue Jul 22, 2016
Closed
@ncdc
Copy link
Member

ncdc commented Jul 26, 2016

@cjcullen this is not test-specific issue and instead is a problem with kubectl trying to use the discovery client to get a list of the apiserver's resources. Somewhere along the line, it's receiving a 404 when it shouldn't be. Without GKE master logs, it will be impossible to track this down. I'm reassigning to you for now but I'd be happy to help if there's some way to get at the master logs.

@ncdc ncdc assigned cjcullen and unassigned ncdc Jul 26, 2016
@k8s-github-robot
Copy link
Author

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

Failed: [k8s.io] Kubectl client [k8s.io] Simple pod should support inline execution and attach {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:402
Expected error:
    <*errors.errorString | 0xc820c8c1d0>: {
        s: "Error running &{/workspace/kubernetes/platforms/linux/amd64/kubectl [kubectl --server=https://107.178.222.21 --kubeconfig=/workspace/.kube/config --namespace=e2e-tests-kubectl-elqba run run-test --image=gcr.io/google_containers/busybox:1.24 --restart=OnFailure --attach=true --stdin -- sh -c cat && echo 'stdin closed'] []  0xc820c600e0  error: google: could not find default credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.\n [] <nil> 0xc820c60000 exit status 1 <nil> true [0xc820c76008 0xc820c76030 0xc820c76040] [0xc820c76008 0xc820c76030 0xc820c76040] [0xc820c76010 0xc820c76028 0xc820c76038] [0xab5420 0xab5580 0xab5580] 0xc820c7c1e0}:\nCommand stdout:\n\nstderr:\nerror: google: could not find default credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.\n\nerror:\nexit status 1\n",
    }
    Error running &{/workspace/kubernetes/platforms/linux/amd64/kubectl [kubectl --server=https://107.178.222.21 --kubeconfig=/workspace/.kube/config --namespace=e2e-tests-kubectl-elqba run run-test --image=gcr.io/google_containers/busybox:1.24 --restart=OnFailure --attach=true --stdin -- sh -c cat && echo 'stdin closed'] []  0xc820c600e0  error: google: could not find default credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
     [] <nil> 0xc820c60000 exit status 1 <nil> true [0xc820c76008 0xc820c76030 0xc820c76040] [0xc820c76008 0xc820c76030 0xc820c76040] [0xc820c76010 0xc820c76028 0xc820c76038] [0xab5420 0xab5580 0xab5580] 0xc820c7c1e0}:
    Command stdout:

    stderr:
    error: google: could not find default credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.

    error:
    exit status 1

not to have occurred

@k8s-github-robot
Copy link
Author

k8s-github-robot commented Aug 2, 2016 •
edited by rmmh
Loading

Builds:
kubernetes-e2e-gce 21031 21094
kubernetes-e2e-gke 13343

Failed: [k8s.io] Kubectl client [k8s.io] Simple pod should support inline execution and attach {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:403
Expected error:
    <*errors.errorString | 0xc820a29630>: {
        s: "Error running &{/workspace/kubernetes/platforms/linux/amd64/kubectl [kubectl --server=https://104.197.252.65 --kubeconfig=/workspace/.kube/config --namespace=e2e-tests-kubectl-ja878 run run-test --image=gcr.io/google_containers/busybox:1.24 --restart=OnFailure --attach=true --stdin -- sh -c cat && echo 'stdin closed'] []  0xc8205611a0  error: failed to discover supported resources: the server could not find the requested resource\n [] <nil> 0xc8205619a0 exit status 1 <nil> true [0xc8204ce688 0xc8204ce708 0xc8204ce728] [0xc8204ce688 0xc8204ce708 0xc8204ce728] [0xc8204ce698 0xc8204ce6d8 0xc8204ce718] [0xab8b80 0xab8ce0 0xab8ce0] 0xc820831980}:\nCommand stdout:\n\nstderr:\nerror: failed to discover supported resources: the server could not find the requested resource\n\nerror:\nexit status 1\n",
    }
    Error running &{/workspace/kubernetes/platforms/linux/amd64/kubectl [kubectl --server=https://104.197.252.65 --kubeconfig=/workspace/.kube/config --namespace=e2e-tests-kubectl-ja878 run run-test --image=gcr.io/google_containers/busybox:1.24 --restart=OnFailure --attach=true --stdin -- sh -c cat && echo 'stdin closed'] []  0xc8205611a0  error: failed to discover supported resources: the server could not find the requested resource
     [] <nil> 0xc8205619a0 exit status 1 <nil> true [0xc8204ce688 0xc8204ce708 0xc8204ce728] [0xc8204ce688 0xc8204ce708 0xc8204ce728] [0xc8204ce698 0xc8204ce6d8 0xc8204ce718] [0xab8b80 0xab8ce0 0xab8ce0] 0xc820831980}:
    Command stdout:

    stderr:
    error: failed to discover supported resources: the server could not find the requested resource

    error:
    exit status 1

not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2003

@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 Aug 2, 2016
@Random-Liu Random-Liu mentioned this issue Aug 12, 2016
Merged
This was referenced Aug 18, 2016
Closed
Closed
Closed
Closed
@k8s-github-robot k8s-github-robot mentioned this issue Aug 28, 2016
Closed
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @cjcullen

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

@k8s-github-robot k8s-github-robot mentioned this issue Sep 1, 2016
Closed
@krousey
Copy link
Contributor

krousey commented Sep 1, 2016

@cjcullen This has been marked with the "needs attention" label and needs to be addressed for the 1.4 release. Could you please

  • close if it's fixed
  • update on your progress to fix it
  • make a case for it not to block the release
  • or find a new owner who can do one of the above soon.

Once you or the new owner update this issue and are actively working on it, you can remove the "needs attention" label.

@cjcullen
Copy link
Member

cjcullen commented Sep 1, 2016

I'll take a look tomorrow.

@smarterclayton
Copy link
Contributor

This may be correlated with #32009 and the attendant ones. This is older than that particular error, but it may be the same symptom on either end. Those are not GKE specific though, so it could be a different failure, but manifesting in the same way.

@k8s-github-robot k8s-github-robot mentioned this issue Sep 3, 2016
Closed
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @cjcullen

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

@k8s-github-robot
Copy link
Author

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

Failed: [k8s.io] Kubectl client [k8s.io] Simple pod should support inline execution and attach {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:401
Expected
    <string>: Waiting for pod e2e-tests-kubectl-062fs/run-test-2-rxyy1 to be running, status is Pending, pod ready: false

to contain substring
    <string>: stdin closed

@smarterclayton
Copy link
Contributor

Different failure now.

@smarterclayton
Copy link
Contributor

There have been races in attach before - I know we carry patches on Docker 1.10 to deal with some of them. It could also be something fixed in 1.4 that we didn't backport because of complexity.

The docker version in the 1.3.7-beta.0 tests on gke-staging-parallel is

time="2016-09-08T21:01:38.181250647Z" level=info msg="Docker daemon" commit=b9f10c9 graphdriver=aufs version=1.11.2

@k8s-github-robot k8s-github-robot mentioned this issue Sep 9, 2016
Closed
This was referenced Jan 6, 2017
Closed
Closed
Closed
This was referenced Jan 15, 2017
Closed
Closed
This was referenced Jan 22, 2017
Closed
Closed
Closed
This was referenced Jan 30, 2017
Closed
Closed
Closed
This was referenced Feb 24, 2017
Closed
Closed
@calebamiles calebamiles added the sig/cli Categorizes an issue or PR as relevant to SIG CLI. label Feb 28, 2017
@k8s-github-robot k8s-github-robot mentioned this issue Feb 28, 2017
Closed
This was referenced Mar 6, 2017
Closed
Closed
This was referenced Mar 19, 2017
Closed
Closed
Closed
This was referenced Mar 28, 2017
Closed
Closed
Closed
Closed
This was referenced Apr 6, 2017
Closed
Closed
Closed
Closed
@k8s-github-robot k8s-github-robot mentioned this issue Apr 28, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cjcullen cjcullen

Labels
area/docker kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/cli Categorizes an issue or PR as relevant to SIG CLI.
Projects
None yet
Milestone
v1.5
Development

No branches or pull requests
10 participants
@ncdc @dims @krousey @calebamiles @smarterclayton @cjcullen @bgrant0607 @pwittrock @saad-ali @k8s-github-robot