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_node/privileged_test gets Unexpected Error executing in Docker Container: 7 #24508

Closed
pwittrock opened this issue Apr 20, 2016 · 15 comments
Closed

e2e_node/privileged_test gets Unexpected Error executing in Docker Container: 7 #24508

pwittrock opened this issue Apr 20, 2016 · 15 comments
Labels
area/node-e2e kind/flake Categorizes issue or PR as related to a flaky test. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@pwittrock
Copy link
Member

15:40:09 STEP: Creating a privileged pod
15:40:09 STEP: Executing privileged command on privileged container
15:40:09 STEP: Exec-ing into container over http. Running command: curl -q 'http://172.17.0.2:8080/shell?shellCommand=ip+link+add+dummy1+type+dummy'
15:40:09
15:40:09 ------------------------------
15:40:09 • Failure [10.173 seconds]
15:40:09 PrivilegedPod
15:40:09 /var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/test/e2e_node/privileged_test.go:84
15:40:09 should test privileged pod [It]
15:40:09 /var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/test/e2e_node/privileged_test.go:83
15:40:09
15:40:09 Error running command "curl -q 'http://172.17.0.2:8080/shell?shellCommand=ip+link+add+dummy1+type+dummy'": error executing remote command: error executing command in container: Error executing in Docker Container: 7
15:40:09 Expected error:
15:40:09 <*errors.errorString | 0xc8204ca400>: {
15:40:09 s: "error executing remote command: error executing command in container: Error executing in Docker Container: 7",
15:40:09 }
15:40:09 error executing remote command: error executing command in container: Error executing in Docker Container: 7
15:40:09 not to have occurred
15:40:09
15:40:09 /var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/test/e2e_node/privileged_test.go:149
@pwittrock pwittrock added sig/node Categorizes an issue or PR as relevant to SIG Node. kind/flake Categorizes issue or PR as related to a flaky test. labels Apr 20, 2016
@pwittrock
Copy link
Member Author

@yujuhong Let me know if you are the right person to assign to

@pwittrock pwittrock mentioned this issue Apr 20, 2016
Merged
@yujuhong
Copy link
Contributor

https://console.cloud.google.com/storage/browser/kubernetes-jenkins/pr-logs/pull/24429/node-pull-build-e2e-test/2152

STEP: Creating a privileged pod
STEP: Executing privileged command on privileged container
STEP: Exec-ing into container over http. Running command: curl -q 'http://172.17.0.2:8080/shell?shellCommand=ip+link+add+dummy1+type+dummy'

------------------------------
• Failure [10.173 seconds]
PrivilegedPod
/var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/test/e2e_node/privileged_test.go:84
  should test privileged pod [It]
  /var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/test/e2e_node/privileged_test.go:83

  Error running command "curl -q 'http://172.17.0.2:8080/shell?shellCommand=ip+link+add+dummy1+type+dummy'": error executing remote command: error executing command in container: Error executing in Docker Container: 7
  Expected error:
      <*errors.errorString | 0xc8204ca400>: {
          s: "error executing remote command: error executing command in container: Error executing in Docker Container: 7",
      }
      error executing remote command: error executing command in container: Error executing in Docker Container: 7
  not to have occurred

  /var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/test/e2e_node/privileged_test.go:149
------------------------------

The error code is from curl: cURL Error (7): couldn't connect to host

/cc the original test author @ArtfulCoder

@jayunit100 jayunit100 mentioned this issue Apr 20, 2016
Closed
@ArtfulCoder
Copy link
Contributor

test has been green for a while?

http://kubekins.dls.corp.google.com/view/Critical%20Builds/job/kubernetes-e2e-gce/15238/testReport/(root)/Kubernetes%20e2e%20suite/_k8s_io__PrivilegedPod_should_test_privileged_pod/history/

@yujuhong
Copy link
Contributor

@ArtfulCoder this is a ported test in the node e2e suite. The ported test is functionally the same as the original test, with minor changes to for the node e2e test environment.

@ArtfulCoder
Copy link
Contributor

Did it ever pass in the node e2e test env ?

@yujuhong
Copy link
Contributor

Yes, node e2e runs per-PR builds, and this is just one failure/flake.

@yujuhong
Copy link
Contributor

@ArtfulCoder: the suite: http://kubekins.dls.corp.google.com:8081/job/node-pull-build-e2e-test/
The test: https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/privileged_test.go

This was referenced Apr 25, 2016
Merged
Merged
@yujuhong
Copy link
Contributor

yujuhong commented May 3, 2016

@ArtfulCoder would you mind taking a look?

@fabioy fabioy mentioned this issue May 3, 2016
Merged
@hongchaodeng hongchaodeng mentioned this issue May 11, 2016
Merged
@yujuhong yujuhong removed their assignment May 24, 2016
@yujuhong
Copy link
Contributor

This hasn't happened for a while and I'm not actively looking at it. Unassign myself for now.

@fejta
Copy link
Contributor

fejta commented May 25, 2016

Assigned to @ArtfulCoder per @yujuhong comment

@dchen1107
Copy link
Member

Last 50 runs, there is no failure. I am closing it for now. Please re-open it if occured again.

@timstclair
Copy link

I just saw this again from the PR builder: https://storage.cloud.google.com/kubernetes-jenkins/pr-logs/pull/24771/node-pull-build-e2e-test/8199/build-log.txt

@timstclair timstclair reopened this May 27, 2016
@timstclair timstclair mentioned this issue May 27, 2016
Merged
@yujuhong
Copy link
Contributor

yujuhong commented Jun 6, 2016

Let's close this one in favor of the automatically-filed issue #26297

@yujuhong yujuhong closed this as completed Jun 6, 2016
@yujuhong yujuhong mentioned this issue Jun 6, 2016
Closed
@jingxu97
Copy link
Contributor

I see the same error in this run
https://pantheon.corp.google.com/storage/browser/kubernetes-jenkins/pr-logs/pull/27576/node-pull-build-e2e-test/10954/

@jingxu97 jingxu97 reopened this Jun 17, 2016
@yujuhong
Copy link
Contributor

Dup of #27498

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/node-e2e kind/flake Categorizes issue or PR as related to a flaky test. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@fejta @ArtfulCoder @timstclair @Random-Liu @dchen1107 @pwittrock @yujuhong @jingxu97