-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[test-failed]: X-Pack API Integration Tests.x-pack/test/api_integration/apis/telemetry/opt_in·ts - apis Telemetry /api/telemetry/v2/optIn API should support sending false #51522
Comments
Pinging @elastic/kibana-test-triage (failed-test) |
Pinging @elastic/kibana-stack-services (Team:Stack Services) |
Pinging @elastic/pulse (Team:Pulse) |
This will fail on cloud since we do not allow changing opt in status on cloud (configured via I believe at the moment this is only skipped for cloud, how can i double check? If so I believe we can close this. |
@Bamieh , thanks when you say we don't allowing changing opt in status on cloud, who is we? Would you say this is not something supported for a customer to do on cloud? |
@liza-mae Cloud users cannot change this kibana config, hence cloud users will not be able to set opt_in to false via the API. |
Thanks @Bamieh ! We should create a PR to skip this test for cloud then and reference this issue as the explanation as to why it is skipped. |
@liza-mae awesome! where do we do that? |
@Bamieh, in file for the following tests:
I was thinking instead of skipping them on cloud, we can verify these commands get rejected on cloud (gives us a better test scenario). We recently added an isCloud() method, so we can use something as follows: if ((await PageObjects.common.isCloud())) { |
Version: 7.6 |
I had a case on staging (not the above) where this command POST /api/telemetry/v2/optIn actually succeeded with 200 response code, which is incorrect. The correct response is 400 {"error":"Not allowed to change Opt-in Status."}. Reference Results: elastic+estf-cloud-kibana-tests/41/testReport |
@liza-mae added to fix in 7.7 |
Version: 7.6.1 |
Pinging @elastic/kibana-core (Team:Core) |
Version: 7.5
Class: X-Pack API Integration Tests.x-pack/test/api_integration/apis/telemetry/opt_in·ts
Test Failures: 2
Other Tests:
X-Pack API Integration Tests.x-pack/test/api_integration/apis/telemetry/opt_in·ts.apis Telemetry /api/telemetry/v2/optIn API should support sending true
Stack Trace:
Error: expected 200 "OK", got 400 "Bad Request"
at Test._assertStatus (/var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/node/linux-immutable/ci/cloud/build/kibana/node_modules/supertest/lib/test.js:268:12)
at Test._assertFunction (/var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/node/linux-immutable/ci/cloud/build/kibana/node_modules/supertest/lib/test.js:283:11)
at Test.assert (/var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/node/linux-immutable/ci/cloud/build/kibana/node_modules/supertest/lib/test.js:173:18)
at assert (/var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/node/linux-immutable/ci/cloud/build/kibana/node_modules/supertest/lib/test.js:131:12)
at /var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/node/linux-immutable/ci/cloud/build/kibana/node_modules/supertest/lib/test.js:128:5
at Test.Request.callback (/var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/node/linux-immutable/ci/cloud/build/kibana/node_modules/superagent/lib/node/index.js:718:3)
at parser (/var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/node/linux-immutable/ci/cloud/build/kibana/node_modules/superagent/lib/node/index.js:906:18)
at IncomingMessage.res.on (/var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/node/linux-immutable/ci/cloud/build/kibana/node_modules/superagent/lib/node/parsers/json.js:19:7)
at endReadableNT (_stream_readable.js:1103:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
Platform: cloud
Build Num: 24
The text was updated successfully, but these errors were encountered: