-
Notifications
You must be signed in to change notification settings - Fork 71
[slice] Extend e2e test for cube failure #1003
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
Conversation
| }) | ||
|
|
||
| ginkgo.By("Checking that a new Slice is created", func() { | ||
| ginkgo.By(fmt.Sprintf("Setting the old cube %s to unhealthy", oldCube), func() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be done before the SliceState is set to error
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both should work, but you are right, this looks more realistic. Updated.
| }, utils.Timeout, utils.Interval).Should(gomega.Succeed()) | ||
| }, nodeName) | ||
| }) | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we verify that Workload's status.schedulingStats contain the eviction?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
|
LGTM |
Description
We want to validate that after cube failure, the re-created slice includes only healthy cubes.
Issue
Testing