[ML] Migration test should use different assertions depending on the old cluster version #37077
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
davidkyle
added
>test-failure
|
Pinging @elastic/ml-core |
This was referenced Jan 3, 2019
|
Now that we have two different versions on the 6.6 branch this change needs to be in 6.6 too. I'll backport it. |
droberts195
pushed a commit
that referenced
this pull request
Jan 31, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MlMigrationFullClusterRestartIT is a full cluster restart test. If the old cluster is v6.6.0 or later then the configurations are already in index documents and don't need to be migrated. This change removes the wait for migration check for those clusters.
The test started failing after the v6.6 branch was cut
Closes #36816