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

ci-kubernetes-kubemark-500-gce failing on 1.14 & 1.15 #87200

Closed
jkaniuk opened this issue Jan 14, 2020 · 10 comments
Closed

ci-kubernetes-kubemark-500-gce failing on 1.14 & 1.15 #87200

jkaniuk opened this issue Jan 14, 2020 · 10 comments

Comments

@jkaniuk
Copy link
Contributor

@jkaniuk jkaniuk commented Jan 14, 2020

Which jobs are failing:
ci-kubernetes-kubemark-500-gce-stable2
ci-kubernetes-kubemark-500-gce-stable3

Which test(s) are failing:
setting up the tests

Since when has it been failing:
since change to using per release perf-tests repository branches

Testgrid link:
https://k8s-testgrid.appspot.com/sig-scalability-kubemark#kubemark-1.15-500
https://k8s-testgrid.appspot.com/sig-scalability-kubemark#kubemark-1.14-500

Reason for failure:

W0114 15:32:11.714] I0114 15:32:11.714357   25155 util.go:71] 8/9 targets are ready
W0114 15:32:11.764] F0114 15:32:11.751347   25155 clusterloader.go:236] Error while setting up prometheus stack: timed out waiting for the condition

Anything else we need to know:

@jkaniuk

This comment has been minimized.

Copy link
Contributor Author

@jkaniuk jkaniuk commented Jan 14, 2020

/assign

@jkaniuk

This comment has been minimized.

Copy link
Contributor Author

@jkaniuk jkaniuk commented Jan 14, 2020

/sig scalability

@jkaniuk

This comment has been minimized.

Copy link
Contributor Author

@jkaniuk jkaniuk commented Jan 20, 2020

Fixed
/close

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

@k8s-ci-robot k8s-ci-robot commented Jan 20, 2020

@jkaniuk: Closing this issue.

In response to this:

Fixed
/close

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.

@justaugustus

This comment has been minimized.

Copy link
Member

@justaugustus justaugustus commented Jan 20, 2020

@jkaniuk -- There is no information whatsoever on how this was fixed. I'd expect that for a failing test issue.

/reopen

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

@k8s-ci-robot k8s-ci-robot commented Jan 20, 2020

@justaugustus: Reopened this issue.

In response to this:

@jkaniuk -- There is no information whatsoever on how this was fixed. I'd expect that for a failing test issue.

/reopen

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.

@k8s-ci-robot k8s-ci-robot reopened this Jan 20, 2020
@justaugustus

This comment has been minimized.

Copy link
Member

@justaugustus justaugustus commented Jan 20, 2020

@jkaniuk

This comment has been minimized.

Copy link
Contributor Author

@jkaniuk jkaniuk commented Jan 20, 2020

Older perf-tests branches (1.14, 1.15) have some problems with setting up Prometheus stack in kubemark tests.
Kubemark periodic tests were changed to use release-1.16 perf-tests branch - PR was linked above.

This solution takes less time than debugging all issues on those branches but in the same time it does not invalidate the promise/reason for creation of perf-tests branches - so that changes on perf-tests master would not break presubmits/release breaking tests on old releases.

In general, perf-tests branches should match kubernetes branches, however value of keeping purity of such assignments on old branches is probably not worth time spent on debugging all issues on them.
This assignment should be eventually consistent, as new releases would have 1 to 1 mapping to perf-tests, and old branches will be gradually phased out.

@jkaniuk

This comment has been minimized.

Copy link
Contributor Author

@jkaniuk jkaniuk commented Jan 22, 2020

Tests are green for last few days
/close

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

@k8s-ci-robot k8s-ci-robot commented Jan 22, 2020

@jkaniuk: Closing this issue.

In response to this:

Tests are green for last few days
/close

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
Projects
None yet
3 participants
You can’t perform that action at this time.