Closed ofiriro3 closed 1 year ago
Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security Posture)
We should not use the ingest pipeline for the latest findings index
I see that when deleting the asset, there is also an error - I am wondering if it can be related:
Error: error deleting component template logs-cloud_security_posture.findings@custom
at deleteComponentTemplate (/Users/ofirlapid/dvlp/kibana/forks/ofiriro3/kibana/x-pack/plugins/fleet/server/services/epm/packages/remove.ts:202:13)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Promise.all (index 2)
at deleteAssets (/Users/ofirlapid/dvlp/kibana/forks/ofiriro3/kibana/x-pack/plugins/fleet/server/services/epm/packages/remove.ts:173:5)
at removeInstallation (/Users/ofirlapid/dvlp/kibana/forks/ofiriro3/kibana/x-pack/plugins/fleet/server/services/epm/packages/remove.ts:64:3)
at deletePackageHandler (/Users/ofirlapid/dvlp/kibana/forks/ofiriro3/kibana/x-pack/plugins/fleet/server/routes/epm/handlers.ts:380:17)
at Router.handle (/Users/ofirlapid/dvlp/kibana/forks/ofiriro3/kibana/node_modules/@kbn/core-http-router-server-internal/target_node/src/router.js:163:30)
at handler (/Users/ofirlapid/dvlp/kibana/forks/ofiriro3/kibana/node_modules/@kbn/core-http-router-server-internal/target_node/src/router.js:124:50)
at exports.Manager.execute (/Users/ofirlapid/dvlp/kibana/forks/ofiriro3/kibana/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at Object.internals.handler (/Users/ofirlapid/dvlp/kibana/forks/ofiriro3/kibana/node_modules/@hapi/hapi/lib/handler.js:46:20)
at exports.execute (/Users/ofirlapid/dvlp/kibana/forks/ofiriro3/kibana/node_modules/@hapi/hapi/lib/handler.js:31:20)
at Request._lifecycle (/Users/ofirlapid/dvlp/kibana/forks/ofiriro3/kibana/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/Users/ofirlapid/dvlp/kibana/forks/ofiriro3/kibana/node_modules/@hapi/hapi/lib/request.js:281:9)
After multiple attempts to reproduce, it seems that the bug is not deterministic.
It is a bit difficult to understand what is the root cause for this bug to happen
It appears that the root cause of this problem was that the latest index used the same ingest pipeline as the findings index. I created a new ingest pipeline for the latest index (as @CohenIdo suggested). It seems to solve it. I am now verifying it
Describe the bug: When running Kibana locally and trying to upgrade the CSP integration version, the ingest manager throws an error.
Steps to reproduce:
elastic-package stack up --version 8.5.0-SNAPSHOT -v -d
)manifest.yml
version
.packages/cloud_security_posture
path runelastic-package build
and thenelastic-package stack up -v -d --services package-registry
Expected behavior: The ingest manager should not throw errors.
Any additional context: Kibana commit - 875a624179a1191f4219da11aa9740b2f6c15f8b