Report error root cause if available

[r00tu53r]

Return root cause (if available) for errors returned from Elasticsearch. This helps debugging errors with respect to ingest pipelines or other errors reported when interacting with Elasticsearch. Example -

Before:

$ elastic-package test pipeline
Run pipeline tests for the package
Error: error running package pipeline tests: could not complete test run: installing ingest pipelines failed: installing pipelines failed: unexpected response status for PutPipeline (400): 400 Bad Request (pipelineName: default-1638926343429676922): elasticsearch error (type=script_exception): compile error

After:

$ elastic-package test pipeline
Run pipeline tests for the package
Error: error running package pipeline tests: could not complete test run: installing ingest pipelines failed: installing pipelines failed: unexpected response status for PutPipeline (400): 400 Bad Request (pipelineName: default-1638926754640971882): elasticsearch error (type=script_exception): compile error
Root cause:
[
  {
    "type": "script_exception",
    "reason": "compile error",
    "processor_type": "dissect",
    "script_stack": [
      "... _principal_name.contains('\\')",
      "                             ^---- HERE"
    ],
    "script": "ctx?.sqlserver?.audit?.server_principal_name != null \u0026\u0026 ctx?.sqlserver?.audit?.server_principal_name.contains('\\')",
    "lang": "painless",
    "position": {
      "offset": 110,
      "start": 85,
      "end": 114
    },
    "suppressed": [
      {
        "type": "parse_exception",
        "reason": "processor [set] doesn't support one or more provided configuration parameters [ignore_missing]",
        "processor_type": "set"
      },
      {
        "type": "parse_exception",
        "reason": "processor [set] doesn't support one or more provided configuration parameters [ignore_missing]",
        "processor_type": "set"
      },
      {
        "type": "parse_exception",
        "reason": "processor [set] doesn't support one or more provided configuration parameters [ignore_missing]",
        "processor_type": "set"
      },
      {
        "type": "parse_exception",
        "reason": "processor [set] doesn't support one or more provided configuration parameters [ignore_missing]",
        "processor_type": "set"
      }
    ]
  }
]

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2021-12-08T02:28:39.880+0000

• Duration: 31 min 14 sec

• Commit: 9d5c22a

Test stats 🧪

Test	Results
Failed	0
Passed	455
Skipped	4
Total	459

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[mtojek]

Hi Sai,

Thanks for your contribution!

Could you please double-check if the verbose mode doesn't mess up the CLI table with test results?

elastic-package test pipeline -v

If it's fine, I'm happy to merge it.

[r00tu53r]

Hi Marcin,

Thank you. I checked the output for elastic-package test pipeline -v for cases where -

1. All pipeline tests passed
2. Some tests failed
3. Some with pipeline errors (i.e. syntax error in pipeline)

For cases 1 & 2 the CLI table was displayed as expected. The 3rd case it isn't applicable. If I've misunderstood please let me know.

[mtojek]

Thanks for the contribution and testing, let's get this one in!