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

[Security Solution] Migration of the .asset-criticality.asset-criticality-<space-id> index does not work on cloud #197211

Closed
MadameSheema opened this issue Oct 22, 2024 · 4 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience fixed impact:critical This issue should be addressed immediately due to a critical level of impact on the product. QA:Needs Validation Issue needs to be validated by QA Team:Entity Analytics Security Entity Analytics Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed

Comments

@MadameSheema
Copy link
Member

Describe the bug:

  • Migration of the .asset-criticality.asset-criticality-<space-id> index does not work on cloud

Kibana/Elasticsearch Stack version:

8.16.0 - BC1

Initial setup:

  • To have a 8.15.3 deployment with some asset criticality configured.

Steps to reproduce:

  1. Upgrade to 8.16.0

Current behavior:

  • When you check the structure of the index is the old one, it does not contain the new fields.
  • When checking the logs, the output of the migration is: Task "security-solution-ea-asset-criticality-ecs-migration" finished. Updated documents: 0, failures: 0

Expected behavior:

  • The structure of the index should be the new one, including the new fields.
  • The migration task should find the documents with the old structure
@MadameSheema MadameSheema added bug Fixes for quality problems that affect the customer experience impact:critical This issue should be addressed immediately due to a critical level of impact on the product. Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Entity Analytics Security Entity Analytics Team triage_needed labels Oct 22, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-entity-analytics (Team:Entity Analytics)

@machadoum
Copy link
Member

Backport PR to 8.16 is here elastic/elasticsearch#115307

@machadoum machadoum added fixed QA:Needs Validation Issue needs to be validated by QA labels Oct 22, 2024
@MadameSheema
Copy link
Member Author

Tested on 8.16.0-BC2, now the migration seems to work :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience fixed impact:critical This issue should be addressed immediately due to a critical level of impact on the product. QA:Needs Validation Issue needs to be validated by QA Team:Entity Analytics Security Entity Analytics Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed
Projects
None yet
Development

No branches or pull requests

3 participants