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.

Sign up for GitHub

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

Jump to bottom

[8.0] CCS Fail Test Mode (#125997) #126526

Closed
wants to merge 1 commit into from
Closed

[8.0] CCS Fail Test Mode (#125997) #126526

wants to merge 1 commit into from

Conversation

cuff-links
Copy link
Contributor

Backport

This will backport the following commits from main to 8.0:

Questions ?

Please refer to the Backport tool documentation

@cuff-links
CCS Fail Test Mode (elastic#125997)
44b6fde 
* Added the search.check_ccs_compatibility flag

* Moved up the level on the logging statements for ES Args so we can debug locally.

* Updated snapshots to reflect new flag that was added.

(cherry picked from commit 68ab355)
@cuff-links cuff-links enabled auto-merge (squash) February 28, 2022 20:54
@kibana-ci
Copy link
Collaborator

kibana-ci commented Feb 28, 2022 •
edited
Loading

💔 Build Failed

Failed CI Steps

Test Failures

  • [job] [logs] Jest Integration Tests #1 / Fleet preconfiguration rest Reset all policy Works and reset all preconfigured policies
  • [job] [logs] Jest Integration Tests #1 / Fleet preconfiguration rest Reset one preconfigured policy Works and reset one preconfigured policies if the policy is already deleted (with a ghost package policy)
  • [job] [logs] Jest Integration Tests #1 / Fleet preconfiguration rest Reset one preconfigured policy Works and reset one preconfigured policies if the policy was deleted with a preconfiguration deletion record
  • [job] [logs] Jest Integration Tests #1 / Fleet preconfiguration rest Reset one preconfigured policy Works if the preconfigured policies already exists with a missing package policy
  • [job] [logs] Jest Integration Tests #1 / migration actions cloneIndex resolves left index_not_found_exception if the source index does not exist
  • [job] [logs] Jest Integration Tests #1 / migration actions cloneIndex resolves left with a retryable_es_client_error if clone target already exists but takes longer than the specified timeout before turning yellow
  • [job] [logs] Jest Integration Tests #1 / migration actions cloneIndex resolves right after waiting for index status to be yellow if clone target already existed
  • [job] [logs] Jest Integration Tests #1 / migration actions cloneIndex resolves right if cloning into a new target index
  • [job] [logs] Jest Integration Tests #1 / migration actions fetchIndices resolves right empty record if no indices were found
  • [job] [logs] Jest Integration Tests #1 / migration actions fetchIndices resolves right record with found indices
  • [job] [logs] Jest Integration Tests #1 / migration actions reindex & waitForReindexTask resolves left incompatible_mapping_exception if all reindex failures are due to a strict_dynamic_mapping_exception
  • [job] [logs] Jest Integration Tests #1 / migration actions reindex & waitForReindexTask resolves right and excludes all documents not matching the unusedTypesQuery
  • [job] [logs] Jest Integration Tests #1 / migration actions reindex & waitForReindexTask resolves right and proceeds to add missing documents if there are some existing docs conflicts
  • [job] [logs] Jest Integration Tests #1 / migration actions reindex & waitForReindexTask resolves right when reindex succeeds with reindex script
  • [job] [logs] Jest Integration Tests #1 / migration actions reindex & waitForReindexTask resolves right when reindex succeeds without reindex script
  • [job] [logs] Jest Integration Tests #1 / migration actions reindex & waitForReindexTask resolves right, ignores version conflicts and does not update existing docs when reindex multiple times
  • [job] [logs] Jest Integration Tests #1 / migration actions removeWriteBlock rejects if there is a non-retryable error
  • [job] [logs] Jest Integration Tests #1 / migration actions removeWriteBlock resolves right if successful when an index already has a write block
  • [job] [logs] Jest Integration Tests #1 / migration actions removeWriteBlock resolves right if successful when an index does not have a write block
  • [job] [logs] Jest Integration Tests #1 / migration actions setWriteBlock once resolved, prevents further writes to the index
  • [job] [logs] Jest Integration Tests #1 / migration actions setWriteBlock resolves left index_not_found_exception when the index does not exist
  • [job] [logs] Jest Integration Tests #1 / migration actions setWriteBlock resolves right when setting a write block on an index that already has one
  • [job] [logs] Jest Integration Tests #1 / migration actions setWriteBlock resolves right when setting the write block succeeds
  • [job] [logs] Jest Integration Tests #1 / migration actions waitForIndexStatusYellow resolves right after waiting for an index status to be yellow if the index already existed

Metrics [docs]

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@cuff-links
Copy link
Contributor Author

I just found out that the flag upon which this PR depends was not backported. Closing this PR. See #81809

@cuff-links cuff-links closed this Mar 1, 2022
auto-merge was automatically disabled March 1, 2022 20:16

Pull request was closed

@cuff-links cuff-links deleted the backport/8.0/pr-125997 branch March 1, 2022 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
backport
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@cuff-links @kibana-ci