[ES Snapshots Failure] Endpoint tests unable to create data stream from ES archive

[spalger]

A change went into ES that disallowed users with access to a data stream permission to edit the underlying indices powering that data stream. Until we add full support for data-streams to es archiver (#69061) ES is working on a fix to restore this capability elastic/elasticsearch#58381

Endpoint plugin test metadata api when ingest manager is not initialized "before all" hook for "metadata api should not return results"

Error:

{ Error: [illegal_argument_exception] The provided expression [metrics-endpoint.metadata-default] matches a data stream, specify the corresponding concrete indices instead.
    at respond (/dev/shm/workspace/kibana/node_modules/elasticsearch/src/lib/transport.js:349:15)
    at checkRespForFailure (/dev/shm/workspace/kibana/node_modules/elasticsearch/src/lib/transport.js:306:7)
    at HttpConnector.<anonymous> (/dev/shm/workspace/kibana/node_modules/elasticsearch/src/lib/connectors/http.js:173:7)
    at IncomingMessage.wrapper (/dev/shm/workspace/kibana/node_modules/elasticsearch/node_modules/lodash/lodash.js:4929:19)
    at endReadableNT (_stream_readable.js:1145:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
  status: 400,
  displayName: 'BadRequest',
  message:
   '[illegal_argument_exception] The provided expression [metrics-endpoint.metadata-default] matches a data stream, specify the corresponding concrete indices instead.',
  path: '/_bulk',
  query: {},
  body:
   { error:
      { root_cause: [Array],
        type: 'illegal_argument_exception',
        reason:
         'The provided expression [metrics-endpoint.metadata-default] matches a data stream, specify the corresponding concrete indices instead.' },
     status: 400 },
  statusCode: 400,
  response:
   '{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"The provided expression [metrics-endpoint.metadata-default] matches a data stream, specify the corresponding concrete indices instead."}],"type":"illegal_argument_exception","reason":"The provided expression [metrics-endpoint.metadata-default] matches a data stream, specify the corresponding concrete indices instead."},"status":400}',
  toString: [Function],
  toJSON: [Function] }

[jonathan-buttner]

This is strange 🤔 . So this test is actually testing that a failure should occur when the metrics-endpoint.metadata-default data stream is not created. The test intentionally does not have the Ingest Manager perform the setup that would normally install the data stream that is causing the failure here.

Does each test directory in kibana get run in an isolated environment? With this test directory get run with a completely clean ES environment or does it rely on the previous tests cleaning up the ES state after they run?

[spalger]

Each FTR config file gets a new instance of ES and Kibana

[jonathan-buttner]

Closing this as it is no longer relevant. The tests have since been removed from Kibana.