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

Failing test: X-Pack API Integration Tests.x-pack/test/api_integration/apis/fleet/setup·ts - apis Fleet Endpoints fleet_setup should not create or update the fleet_enroll user if called multiple times #72053

Closed
kibanamachine opened this issue Jul 16, 2020 · 6 comments
Assignees
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test Feature:Fleet Fleet team's agent central management project skipped-test Team:Fleet Team label for Observability Data Collection Fleet team v7.9.0

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jul 16, 2020

A test failed on a tracked branch

Error: expected 200 "OK", got 500 "Internal Server Error"
    at Test._assertStatus (/dev/shm/workspace/kibana/node_modules/supertest/lib/test.js:268:12)
    at Test._assertFunction (/dev/shm/workspace/kibana/node_modules/supertest/lib/test.js:283:11)
    at Test.assert (/dev/shm/workspace/kibana/node_modules/supertest/lib/test.js:173:18)
    at assert (/dev/shm/workspace/kibana/node_modules/supertest/lib/test.js:131:12)
    at /dev/shm/workspace/kibana/node_modules/supertest/lib/test.js:128:5
    at Test.Request.callback (/dev/shm/workspace/kibana/node_modules/superagent/lib/node/index.js:718:3)
    at parser (/dev/shm/workspace/kibana/node_modules/superagent/lib/node/index.js:906:18)
    at IncomingMessage.res.on (/dev/shm/workspace/kibana/node_modules/superagent/lib/node/parsers/json.js:19:7)
    at endReadableNT (_stream_readable.js:1145:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jul 16, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-test-triage (failed-test)

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

spalger added a commit that referenced this issue Jul 16, 2020
spalger added a commit that referenced this issue Jul 16, 2020
(cherry picked from commit 0a9f134)
spalger added a commit that referenced this issue Jul 16, 2020
(cherry picked from commit 0a9f134)
@spalger
Copy link
Contributor

spalger commented Jul 16, 2020

10 failures across master, 7.9, and PRs

image

skipped

master: 0a9f134
7.x/7.10: 5bb80fc
7.9: 48b3cb1

@spalger spalger added blocker Feature:Fleet Fleet team's agent central management project skipped-test Team:Fleet Team label for Observability Data Collection Fleet team v7.9.0 labels Jul 16, 2020
@spalger
Copy link
Contributor

spalger commented Jul 16, 2020

cc @elastic/ingest-management

@jen-huang jen-huang self-assigned this Jul 16, 2020
@jen-huang
Copy link
Contributor

This error occurs before the failure:

[00:08:49]                 │ proc [kibana]  error  [13:01:45.279] [warning][process] Error: [epm-packages:system]: version conflict, required seqNo [23], primary term [1]. current document has seqNo [105] and primary term [1]: [version_conflict_engine_exception] [epm-packages:system]: version conflict, required seqNo [23], primary term [1]. current document has seqNo [105] and primary term [1], with { index_uuid="a1TMi6yFSHiXAfM2mkFKvQ" & shard="0" & index=".kibana_2" }

Which is the same error seen in #72102

@jen-huang
Copy link
Contributor

Fixed with #72149

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test Feature:Fleet Fleet team's agent central management project skipped-test Team:Fleet Team label for Observability Data Collection Fleet team v7.9.0
Projects
None yet
Development

No branches or pull requests

4 participants