Kibana: Failing test: X-Pack API Integration Tests.x-pack/test/api_integration/apis/fleet/unenroll_agent·ts - apis Fleet Endpoints fleet_unenroll_agent allow to unenroll using a list of ids

Created on 28 Apr 2020  ·  29Comments  ·  Source: elastic/kibana

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

Ingest Management bug failed-test skipped-test v7.9.0
Source
picture kibanamachine

All 29 comments

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

elasticmachine picture elasticmachine on 28 Apr 2020

New failure: Jenkins Build

kibanamachine picture kibanamachine on 4 May 2020

New failure: Jenkins Build

kibanamachine picture kibanamachine on 4 May 2020

New failure: Jenkins Build

kibanamachine picture kibanamachine on 4 May 2020

New failure: Jenkins Build

kibanamachine picture kibanamachine on 4 May 2020

New failure: Jenkins Build

kibanamachine picture kibanamachine on 4 May 2020

New failure: Jenkins Build

kibanamachine picture kibanamachine on 4 May 2020

@elastic/ingest-management could you look into this please?

mistic picture mistic on 4 May 2020

Pinging @elastic/endpoint-management (Team:Endpoint Management)

elasticmachine picture elasticmachine on 4 May 2020

@nchaulet Can you take a look?

ph picture ph on 4 May 2020

Looking

nchaulet picture nchaulet on 4 May 2020

Fleet was not able to setup because of an error related to the package manager looks like it's fixed now

[00:08:43]                 │ proc [kibana]  error  [09:22:20.146] [warning][process] UnhandledPromiseRejectionWarning: YAMLException: bad indentation of a sequence entry at line 14, column 9:
[00:08:43]                 │ proc [kibana]     - name: @timestamp
[00:08:43]                 │ proc [kibana]             ^
[00:08:43]                 │ proc [kibana]     at generateError (/dev/shm/workspace/install/kibana-7/node_modules/js-yaml/lib/js-yaml/loader.js:167:10)
[00:08:43]                 │ proc [kibana]     at throwError (/dev/shm/workspace/install/kibana-7/node_modules/js-yaml/lib/js-yaml/loader.js:173:9)
[00:08:43]                 │ proc [kibana]     at readBlockSequence (/dev/shm/workspace/install/kibana-7/node_modules/js-yaml/lib/js-yaml/loader.js:962:7)
[00:08:43]                 │ proc [kibana]     at composeNode (/dev/shm/workspace/install/kibana-7/node_modules/js-yaml/lib/js-yaml/loader.js:1358:12)
[00:08:43]                 │ proc [kibana]     at readDocument (/dev/shm/workspace/install/kibana-7/node_modules/js-yaml/lib/js-yaml/loader.js:1519:3)
[00:08:43]                 │ proc [kibana]     at loadDocuments (/dev/shm/workspace/install/kibana-7/node_modules/js-yaml/lib/js-yaml/loader.js:1575:5)
[00:08:43]                 │ proc [kibana]     at load (/dev/shm/workspace/install/kibana-7/node_modules/js-yaml/lib/js-yaml/loader.js:1596:19)
[00:08:43]                 │ proc [kibana]     at safeLoad (/dev/shm/workspace/install/kibana-7/node_modules/js-yaml/lib/js-yaml/loader.js:1618:10)
[00:08:43]                 │ proc [kibana]     at reduce (/dev/shm/workspace/install/kibana-7/x-pack/plugins/ingest_manager/server/services/epm/fields/field.js:227:25)
[00:08:43]                 │ proc [kibana]     at Array.reduce (<anonymous>)
[00:08:43]                 │ proc [kibana]     at loadFieldsFromYaml (/dev/shm/workspace/install/kibana-7/x-pack/plugins/ingest_manager/server/services/epm/fields/field.js:224:31)
[00:08:43]                 │ proc [kibana]     at process._tickCallback (internal/process/next_tick.js:68:7)
[00:08:43]                 │ proc [kibana]     at emitWarning (internal/process/promises.js:97:15)
[00:08:43]                 │ proc [kibana]     at emitPromiseRejectionWarnings (internal/process/promises.js:143:7)
[00:08:43]                 │ proc [kibana]     at process._tickCallback (internal/process/next_tick.js:69:34)
nchaulet picture nchaulet on 4 May 2020

@nchaulet then do you think that test is not flaky and we can close the PR to skip it?

mistic picture mistic on 4 May 2020

Yes you can close the PR to skip it,
I think this could really help to avoid this issue in the future https://github.com/elastic/kibana/pull/61920

nchaulet picture nchaulet on 4 May 2020
👍1

closing for now

mistic picture mistic on 4 May 2020

New failure: Jenkins Build

kibanamachine picture kibanamachine on 20 May 2020

Snippet from the logs:

└-> "before all" hook
  │ info [o.e.c.m.MetadataMappingService] [kibana-ci-immutable-ubuntu-18-tests-xl-1589964441590935549] [.kibana_2/6NmaVv01Tf2Gj2voEu7Rng] update_mapping [_doc]
  │ info [o.e.c.m.MetadataCreateIndexService] [kibana-ci-immutable-ubuntu-18-tests-xl-1589964441590935549] applying create index request using v1 templates []
  │ info [o.e.c.m.MetadataCreateIndexService] [kibana-ci-immutable-ubuntu-18-tests-xl-1589964441590935549] [logs-index_pattern_placeholder] creating index, cause [api], templates [], shards [1]/[1], mappings [_doc]
  │ info [o.e.c.m.MetadataCreateIndexService] [kibana-ci-immutable-ubuntu-18-tests-xl-1589964441590935549] applying create index request using v1 templates []
  │ info [o.e.c.m.MetadataCreateIndexService] [kibana-ci-immutable-ubuntu-18-tests-xl-1589964441590935549] [metrics-index_pattern_placeholder] creating index, cause [api], templates [], shards [1]/[1], mappings [_doc]
  │ info [o.e.c.m.MetadataCreateIndexService] [kibana-ci-immutable-ubuntu-18-tests-xl-1589964441590935549] applying create index request using v1 templates []
  │ info [o.e.c.m.MetadataCreateIndexService] [kibana-ci-immutable-ubuntu-18-tests-xl-1589964441590935549] [events-index_pattern_placeholder] creating index, cause [api], templates [], shards [1]/[1], mappings [_doc]
  │ proc [kibana]   log   [09:49:18.443] [error][ingestManager][plugins] Error connecting to package registry: Not Found
  │ info [o.e.c.m.MetadataMappingService] [kibana-ci-immutable-ubuntu-18-tests-xl-1589964441590935549] [.kibana_2/6NmaVv01Tf2Gj2voEu7Rng] update_mapping [_doc]
└-> allow to unenroll using a list of ids
  └-> "before each" hook: global before each
  └-> "before each" hook
    │ proc [kibana]  error  [09:49:18.493]  Error: Internal Server Error
    │ proc [kibana]     at HapiResponseAdapter.toError (/dev/shm/workspace/install/kibana-7/src/core/server/http/router/response_adapter.js:132:19)
    │ proc [kibana]     at HapiResponseAdapter.toHapiResponse (/dev/shm/workspace/install/kibana-7/src/core/server/http/router/response_adapter.js:86:19)
    │ proc [kibana]     at HapiResponseAdapter.handle (/dev/shm/workspace/install/kibana-7/src/core/server/http/router/response_adapter.js:81:17)
    │ proc [kibana]     at Router.handle (/dev/shm/workspace/install/kibana-7/src/core/server/http/router/router.js:160:34)
    │ proc [kibana]     at process._tickCallback (internal/process/next_tick.js:68:7)
  └- ✖ fail: "apis Fleet Endpoints fleet_unenroll_agent allow to unenroll using a list of ids"

│ proc [kibana] log [09:49:18.443] [error][ingestManager][plugins] Error connecting to package registry: Not Found

That looks suspicious, but it also seems to happen before the test starts...

spalger picture spalger on 20 May 2020

│ proc [kibana] log [09:49:18.443] [error][ingestManager][plugins] Error connecting to package registry: Not Found

This is happening in the beforeEach, so the test probably because of that. This would be fixed if we have a local package registry

nchaulet picture nchaulet on 20 May 2020
👍1

Do you think we should be attempting to recover from that automatically? What does the "Not Found" mean? Do you think that responding with a 500 is the right approach?

spalger picture spalger on 20 May 2020

@nchaulet can you take a look?

ph picture ph on 8 Jun 2020

@spalger Yes I think a 500 is the right response here, as it's an error that is a major error that will block fleet and ingest manager later, the Not Found Error means that we receive a 404 when try to comunicate from Kibana to the Package registry, I think sonja did some work to have better messaging.

I will close it for now

nchaulet picture nchaulet on 8 Jun 2020

New failure: Jenkins Build

kibanamachine picture kibanamachine on 10 Jun 2020

New failure: Jenkins Build

kibanamachine picture kibanamachine on 10 Jun 2020

This is still a problem @nchaulet we should fix it.

ph picture ph on 29 Jun 2020

New failure: Jenkins Build

kibanamachine picture kibanamachine on 16 Jul 2020

^ This latest failure is due to the same version conflict error seen in #72102 & #72053

jen-huang picture jen-huang on 16 Jul 2020

13 failures in PRs and 1 failure in 7.x, skipping

image

master: https://github.com/elastic/kibana/commit/55da30d17a7489a95c158b5cea01b5ddb785dbc9
7.x/7.10: https://github.com/elastic/kibana/commit/cb5559a44cac94203dfbca00d3b154c1b1151f95
7.9: https://github.com/elastic/kibana/commit/897cc3400debe27dae9eb8e33118d12f2bb4f7b3

spalger picture spalger on 17 Jul 2020

New failure: Jenkins Build

kibanamachine picture kibanamachine on 17 Jul 2020

Fixed with #72149

jen-huang picture jen-huang on 20 Jul 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

timmolter picture timmolter  ·  3Comments
treussart picture treussart  ·  3Comments
snide picture snide  ·  3Comments
timroes picture timroes  ·  3Comments
spalger picture spalger  ·  3Comments