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

ResizeNode e2e test is flaky #8715

Closed
dchen1107 opened this issue May 22, 2015 · 0 comments · Fixed by #8775
Closed

ResizeNode e2e test is flaky #8715

dchen1107 opened this issue May 22, 2015 · 0 comments · Fixed by #8775
Assignees
Labels
area/test sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.

Comments

@dchen1107
Copy link
Member

This newly introduced e2e test (#8243) is flaky sometimes from Jenkin runs. I personally couldn't reproduced it.

ResizeNodes should be able to add nodes.

/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/resize_nodes.go:337
Expected error:
<*errors.errorString | 0xc20911a010>: {
s: "timeout waiting for cluster size to be 3",
}
timeout waiting for cluster size to be 3
not to have occurred

cc/ @quinton-hoole @jszczepkowski

@dchen1107 dchen1107 added area/test sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. labels May 22, 2015
@jszczepkowski jszczepkowski self-assigned this May 25, 2015
jszczepkowski added a commit to jszczepkowski/kubernetes that referenced this issue May 25, 2015
Extended wait for cluster size timeout in resize nodes e2e test to fix kubernetes#8715.
jackgr pushed a commit to jackgr/kubernetes that referenced this issue May 25, 2015
Extended wait for cluster size timeout in resize nodes e2e test to fix kubernetes#8715.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants