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

[flake] Node e2e: privileged pod operation not permitted #24396

Closed
hongchaodeng opened this issue Apr 18, 2016 · 2 comments
Closed

[flake] Node e2e: privileged pod operation not permitted #24396

hongchaodeng opened this issue Apr 18, 2016 · 2 comments
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@hongchaodeng
Copy link
Contributor

A recent flake happen on node e2e test.

Even though the tests still have a result of success:

SUCCESS! -- 23 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

It showed the following error and exited non-zero:

PrivilegedPod
/var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/test/e2e_node/privileged_test.go:84
I0418 00:49:16.232705    2717 privileged_test.go:154] Deserialized output is map[error:exit status 2 output:RTNETLINK answers: Operation not permitted
]
  should test privileged pod
  /var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/test/e2e_node/privileged_test.go:83
------------------------------
•••I0418 00:49:20.251513    2717 e2e_node_suite_test.go:82] Stopping node services...
E0418 00:49:20.251555    2717 e2e_service.go:83] Failed to stop kubelet.
operation not permitted
E0418 00:49:20.251643    2717 e2e_service.go:89] Failed to stop be-apiserver.
operation not permitted

See log here
@hongchaodeng hongchaodeng mentioned this issue Apr 18, 2016
Merged
@mikedanese mikedanese added sig/node Categorizes an issue or PR as relevant to SIG Node. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Apr 19, 2016
@mikedanese
Copy link
Member

mikedanese commented Apr 19, 2016 •
edited
Loading

http://kubekins.dls.corp.google.com/view/Critical%20Builds/job/kubelet-gce-e2e-ci/1745/consoleFull

cc @pwittrock @kubernetes/sig-node

@yujuhong
Copy link
Contributor

The log message is misleading. "operation not permitted" is the expected output and the logging level is INFO. There is a PR to remove this line.

For #24396 (comment), the failure is

15:08:37 ================================================================
15:09:33 ================================================================
15:09:33 Failure Finished Host tmp-node-e2e-e4982447-e2e-node-ubuntu-trusty-docker9-image Test Suite
15:09:33 
15:09:33 Command [ssh -i /home/jenkins/.ssh/google_compute_engine -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o CheckHostIP=no -o StrictHostKeyChecking=no tmp-node-e2e-e4982447-e2e-node-ubuntu-trusty-docker9-image -- sh -c 'cd /tmp/gcloud-e2e-30265922 && tar -xzvf ./e2e_node_test.tar.gz && ./e2e_node.test --logtostderr --v 2 --build-services=false --node-name=tmp-node-e2e-e4982447-e2e-node-ubuntu-trusty-docker9-image'] failed with error: exit status 1 and output:
15:09:33 Warning: Permanently added 'tmp-node-e2e-e4982447-e2e-node-ubuntu-trusty-docker9-image' (ECDSA) to the list of known hosts.
15:09:33 ./
15:09:33 ./kubelet
15:09:33 ./kube-apiserver
15:09:33 ./e2e_node.test
15:09:33 Running Suite: E2eNode Suite
15:09:33 ============================

This is a dup of #24422

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hongchaodeng @mikedanese @yujuhong