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

UpgradeClusterClientYamlTestSuiteIT tests fail because of deprecation warnings #38412

Closed
jkakavas opened this issue Feb 5, 2019 · 5 comments
Closed
Assignees
Labels
:Data Management/Indices APIs APIs to create and manage indices and templates :ml Machine learning >test-failure Triaged test failures from CI

Comments

@jkakavas
Copy link
Member

jkakavas commented Feb 5, 2019

Came across this in a PR build: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+pull-request-2/7278/console

Example output:

3:04:47 ERROR   0.08s | UpgradeClusterClientYamlTestSuiteIT.test {p0=old_cluster/40_ml_datafeed_crud/Put job and datafeed in old cluster} <<< FAILURES!
13:04:47    > Throwable #1: org.elasticsearch.client.WarningFailureException: method [GET], host [http://[::1]:46781], URI [/_template/.ml-notifications], status line [HTTP/1.1 200 OK]
13:04:47    > Warnings: [[types removal] The response format of get index template requests will change in the next major version. Please start using the `include_type_name` parameter set to `false` in the request to move to the new, typeless response format that will be the default in 7.0.]
13:04:47    > {".ml-notifications":{"order":0,"version":6070099,"index_patterns":[".ml-notifications"],"settings":{"index":{"number_of_shards":"1","auto_expand_replicas":"0-1","unassigned":{"node_left":{"delayed_timeout":"1m"}}}},"mappings":{"audit_message":{"properties":{"job_id":{"type":"keyword"},"level":{"type":"keyword"},"message":{"type":"text","fields":{"raw":{"type":"keyword"}}},"timestamp":{"type":"date"},"node_name":{"type":"keyword"}}}},"aliases":{}}}
13:04:47    > 	at __randomizedtesting.SeedInfo.seed([CA5B3D2C2AEFD704:420F02F68413BAFC]:0)
13:04:47    > 	at org.elasticsearch.client.RestClient$SyncResponseListener.get(RestClient.java:690)
13:04:47    > 	at org.elasticsearch.client.RestClient.performRequest(RestClient.java:218)
13:04:47    > 	at org.elasticsearch.xpack.test.rest.XPackRestTestHelper.lambda$waitForTemplates$1(XPackRestTestHelper.java:79)
13:04:47    > 	at org.elasticsearch.test.ESTestCase.awaitBusy(ESTestCase.java:879)
13:04:47    > 	at org.elasticsearch.test.ESTestCase.awaitBusy(ESTestCase.java:868)
13:04:47    > 	at org.elasticsearch.xpack.test.rest.XPackRestTestHelper.waitForTemplates(XPackRestTestHelper.java:76)
13:04:47    > 	at org.elasticsearch.upgrades.UpgradeClusterClientYamlTestSuiteIT.waitForTemplates(UpgradeClusterClientYamlTestSuiteIT.java:31)
13:04:47    > 	at java.lang.Thread.run(Thread.java:748)
13:04:47    > Caused by: org.elasticsearch.client.WarningFailureException: method [GET], host [http://[::1]:46781], URI [/_template/.ml-notifications], status line [HTTP/1.1 200 OK]
13:04:47    > Warnings: [[types removal] The response format of get index template requests will change in the next major version. Please start using the `include_type_name` parameter set to `false` in the request to move to the new, typeless response format that will be the default in 7.0.]
13:04:47    > {".ml-notifications":{"order":0,"version":6070099,"index_patterns":[".ml-notifications"],"settings":{"index":{"number_of_shards":"1","auto_expand_replicas":"0-1","unassigned":{"node_left":{"delayed_timeout":"1m"}}}},"mappings":{"audit_message":{"properties":{"job_id":{"type":"keyword"},"level":{"type":"keyword"},"message":{"type":"text","fields":{"raw":{"type":"keyword"}}},"timestamp":{"type":"date"},"node_name":{"type":"keyword"}}}},"aliases":{}}}
13:04:47    > 	at org.elasticsearch.client.RestClient$1.completed(RestClient.java:304)
13:04:47    > 	at org.elasticsearch.client.RestClient$1.completed(RestClient.java:294)
13:04:47    > 	at org.apache.http.concurrent.BasicFuture.completed(BasicFuture.java:122)
13:04:47    > 	at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.responseCompleted(DefaultClientExchangeHandlerImpl.java:181)
13:04:47    > 	at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:448)
13:04:47    > 	at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.inputReady(HttpAsyncRequestExecutor.java:338)
13:04:47    > 	at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:265)
13:04:47    > 	at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81)
13:04:47    > 	at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39)
13:04:47    > 	at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:114)
13:04:47    > 	at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162)
13:04:47    > 	at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337)
13:04:47    > 	at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315)
13:04:47    > 	at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276)
13:04:47    > 	at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
13:04:47    > 	at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:591)
13:04:47    > 	... 1 more

This looks similar to #38395 and looks like it can be resolved by dealing with the deprecation warnings in the XPackRestTestHelper

@jkakavas jkakavas added the >test-failure Triaged test failures from CI label Feb 5, 2019
@cbuescher cbuescher self-assigned this Feb 5, 2019
@jkakavas
Copy link
Member Author

jkakavas commented Feb 5, 2019

This needs to be addressed at the same time as #38396 because otherwise, each one will cause the other to fail CI and we'll never be able to merge :)

@colings86 colings86 added :Data Management/Indices APIs APIs to create and manage indices and templates :ml Machine learning labels Feb 5, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

@cbuescher
Copy link
Member

@jkakavas unfortunately the earlier revert of #38419 doesn't fix this but I opened #38431 which I hope will solve at least the ml related failures. Will need to see if anything else turns up while running CI.

cbuescher pushed a commit that referenced this issue Feb 5, 2019
The backport of #38022 introduced types-deprecation warning for get/put template requests
that cause problems on tests master in mixed cluster scenarios. While these warnings are
caught and ignored in regular Rest tests, the get template requests in XPackRestTestHelper
were missed.

Closes #38412
@cbuescher
Copy link
Member

@jkakavas the earlier revert in #38427 should have solved this issue for now, but I also just pushed #38431 that should also fix the issue when we add the backport by @markharwood again later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Indices APIs APIs to create and manage indices and templates :ml Machine learning >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

4 participants