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

[Failing Test] master-blocking:kubeadm-gce-master Test #73880

alejandrox1 opened this Issue Feb 9, 2019 · 3 comments


None yet
3 participants
Copy link

alejandrox1 commented Feb 9, 2019

Which jobs are failing:

Which test(s) are failing:

Since when has it been failing:
Failing since 2/4 at 14:11. k/k diff and k/-test-infra diff.

Testgrid link:

Reason for failure:

W0204 22:23:12.081] 2019/02/04 22:23:12 main.go:297: Something went wrong: encountered 1 errors: [error during ./hack/ --ginkgo.focus=\[Conformance\]|\[Feature:BootstrapTokens\]|\[Feature:NodeAuthorizer\] --minStartupPods=8 --report-dir=/workspace/_artifacts --disable-log-dump=true: exit status 1]
W0204 22:23:12.085] Traceback (most recent call last):
W0204 22:23:12.086]   File "/workspace/./test-infra/jenkins/../scenarios/", line 764, in <module>
W0204 22:23:12.086]     main(parse_args())
W0204 22:23:12.086]   File "/workspace/./test-infra/jenkins/../scenarios/", line 615, in main
W0204 22:23:12.086]     mode.start(runner_args)
W0204 22:23:12.086]   File "/workspace/./test-infra/jenkins/../scenarios/", line 262, in start
W0204 22:23:12.086]     check_env(env, self.command, *args)
W0204 22:23:12.086]   File "/workspace/./test-infra/jenkins/../scenarios/", line 111, in check_env
W0204 22:23:12.087]     subprocess.check_call(cmd, env=env)
W0204 22:23:12.087]   File "/usr/lib/python2.7/", line 186, in check_call
W0204 22:23:12.087]     raise CalledProcessError(retcode, cmd)
W0204 22:23:12.087] subprocess.CalledProcessError: Command '('kubetest', '--dump=/workspace/_artifacts', '--gcp-service-account=/etc/service-account/service-account.json', '--up', '--down', '--test', '--deployment=kubernetes-anywhere', '--provider=skeleton', '--cluster=e2e-1798-1ad8f', '--gcp-network=e2e-1798-1ad8f', '--extract=ci/latest-bazel', '--gcp-zone=us-west1-b', '--kubernetes-anywhere-kubelet-ci-version=latest-bazel', '--kubernetes-anywhere-kubernetes-version=ci-cross/latest', '--test_args=--ginkgo.focus=\\[Conformance\\]|\\[Feature:BootstrapTokens\\]|\\[Feature:NodeAuthorizer\\] --minStartupPods=8', '--timeout=300m', '--kubernetes-anywhere-path=/workspace/', '--kubernetes-anywhere-phase2-provider=kubeadm', '--kubernetes-anywhere-cluster=e2e-1798-1ad8f', '--kubernetes-anywhere-kubeadm-version=gs://kubernetes-release-dev/ci/v1.14.0-alpha.2.287+732cb10019c50e-bazel/bin/linux/amd64/')' returned non-zero exit status 1
E0204 22:23:12.100] Command failed
I0204 22:23:12.101] process 328 exited with code 1 after 10.4m
E0204 22:23:12.101] FAIL: ci-kubernetes-e2e-kubeadm-gce-master

cc @mortent @kacole2 @mariantalla @smourapina

/kind failing-test
/sig cluster-lifecycle


This comment has been minimized.

Copy link

neolit123 commented Feb 10, 2019

/area kubeadm


This comment has been minimized.


This comment has been minimized.

Copy link

k8s-ci-robot commented Feb 11, 2019

@neolit123: Closing this issue.

In response to this:

this is fixed:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment