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: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/infra/metrics_source_configuration·ts - InfraOps app Infrastructure Source Configuration "before all" hook #43221

Closed
kibanamachine opened this issue Aug 13, 2019 · 1 comment · Fixed by #43987
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test

Comments

@kibanamachine
Copy link
Contributor

A test failed on a tracked branch


        { Error: Response Error: 409 Conflict
    at internals.Client._shortcut (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup7/node/linux-immutable/kibana/node_modules/@hapi/wreck/lib/index.js:635:11)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  data:
   { isResponseError: true,
     headers:
      { 'kbn-name': 'kibana',
        'kbn-xpack-sig': '89268b8ad8f0397cbf77afe2d6644afa',
        'content-type': 'application/json; charset=utf-8',
        'cache-control': 'no-cache',
        'content-length': '348',
        date: 'Tue, 13 Aug 2019 21:19:40 GMT',
        connection: 'close' },
     res:
      IncomingMessage {
        _readableState: [ReadableState],
        readable: false,
        _events: [Object],
        _eventsCount: 2,
        _maxListeners: undefined,
        socket: [Socket],
        connection: [Socket],
        httpVersionMajor: 1,
        httpVersionMinor: 1,
        httpVersion: '1.1',
        complete: true,
        headers: [Object],
        rawHeaders: [Array],
        trailers: {},
        rawTrailers: [],
        aborted: false,
        upgrade: false,
        url: '',
        method: null,
        statusCode: 409,
        statusMessage: 'Conflict',
        client: [Socket],
        _consuming: false,
        _dumped: false,
        req: [ClientRequest] },
     payload:
      { message:
         '[config:7.4.0-SNAPSHOT]: version conflict, document already exists (current version [1]): [version_conflict_engine_exception] [config:7.4.0-SNAPSHOT]: version conflict, document already exists (current version [1]), with { index_uuid="JnIcJ4IaRNW-fFng7T6GAA" & shard="0" & index=".kibana_2" }',
        statusCode: 409,
        error: 'Conflict' } },
  isBoom: true,
  isServer: false,
  output:
   { statusCode: 409,
     payload:
      { statusCode: 409,
        error: 'Conflict',
        message: 'Response Error: 409 Conflict' },
     headers: {} },
  reformat: [Function],
  typeof: [Function: Error] }
      

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Aug 13, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-test-triage

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-test A test failure on a tracked branch, potentially flaky-test
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants