[Fleet] Initiating package package installation immediately sets status to "installed" #108649
Labels
bug
Fixes for quality problems that affect the customer experience
Team:Fleet
Team label for Observability Data Collection Fleet team
Kibana version:
8.0.0-SNAPSHOT
Elasticsearch version:
8.0.0-SNAPSHOT
Describe the bug:
When installing a package through the Integrations app, the package status as reported by the API is immediately "installed" even before the Elasticsearch assets are created.
Steps to reproduce:
http://kibana/app/integrations/detail/apm-0.4.0/settings
, install the integrationcurl http://kibana:5601/api/fleet/epm/packages/apm
Expected behavior:
The reported package status is "installing" until all assets are installed.
Provide logs and/or server output (if relevant):
Package status before Elasticsearch assets installed
Package status after Elasticsearch assets installed
Any additional context:
In 8.0 if APM Server is run standalone, we will be relying on the integration package to be installed (importantly, for index templates and ingest pipelines to be created), prior to indexing any events. I would expect the package installation status to be most authoritative.
If the Elasticsearch assets are not installed when the APM Server thinks the package is fully installed, then it may index events before data stream index templates are installed and auto-create classic indices (with default dynamic mappings) instead.
See elastic/apm-server#5914 for background.
The text was updated successfully, but these errors were encountered: