Skip CAS deprecation tests until all nodes upgraded #42974
Merged
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
dnhatn
added
>test
|
Pinging @elastic/es-distributed |
|
Thanks @ywelsch. |
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.
After we moved CAS deprecation check to TransportShardBulkAction (#42641), a mixed cluster consisting of 6.7 and 6.8.1 nodes can issue two deprecation warnings for versioning write requests. The way we deduplicate response headers does not work for warning headers from different versions (maybe we need to improve this?). This commit skips CAS deprecation tests until all nodes on 6.8.1+.
An alternative option is to make
DoSection.checkWarningHeadersmore lenient to accept duplicated warnings (maybe only CAS warnings).Some CI instances: