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.

Sign up for GitHub

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

Jump to bottom

Failing test: EDR Workflows - Response Actions Integration Tests - Serverless Env - Complete.x-pack/test/security_solution_api_integration/test_suites/edr_workflows/response_actions/trial_license_complete_tier/execute·ts - Endpoint plugin @ess @serverless @skipInServerlessMKI Endpoint execute response action "before all" hook for "should not allow execute action without required privilege" #203906

Open
kibanamachine opened this issue Dec 11, 2024 · 22 comments · Fixed by #204405
Open

Failing test: EDR Workflows - Response Actions Integration Tests - Serverless Env - Complete.x-pack/test/security_solution_api_integration/test_suites/edr_workflows/response_actions/trial_license_complete_tier/execute·ts - Endpoint plugin @ess @serverless @skipInServerlessMKI Endpoint execute response action "before all" hook for "should not allow execute action without required privilege" #203906

kibanamachine opened this issue Dec 11, 2024 · 22 comments · Fixed by #204405
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Defend Workflows “EDR Workflows” sub-team of Security Solution

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Dec 11, 2024 •
edited
Loading

A test failed on a tracked branch

EndpointDataLoadingError: mapper_parsing_exception
	Caused by:
		mapper_parsing_exception: No handler for type [bool] declared on field [flag_hugetlb]
	Root causes:
		mapper_parsing_exception: No handler for type [bool] declared on field [flag_hugetlb]
    at updatePackages (setup_fleet_for_endpoint.ts:147:17)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at retryOnError (utils.ts:88:22) {
  meta: [
    {
      name: 'endpoint',
      statusCode: 500,
      error: 'mapper_parsing_exception\n' +
        '\tCaused by:\n' +
        '\t\tmapper_parsing_exception: No handler for type [bool] declared on field [flag_hugetlb]\n' +
        '\tRoot causes:\n' +
        '\t\tmapper_parsing_exception: No handler for type [bool] declared on field [flag_hugetlb]'
    }
  ]
}

First failure: kibana-on-merge - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Dec 11, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Dec 11, 2024
@kibanamachine kibanamachine added the Team:Defend Workflows “EDR Workflows” sub-team of Security Solution label Dec 11, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-defend-workflows (Team:Defend Workflows)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Dec 11, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

mistic added a commit that referenced this issue Dec 11, 2024
@mistic
skip flaky suite (#203906)
ccb0cba
@mistic
Copy link
Member

mistic commented Dec 11, 2024

Skipped.

main: ccb0cba

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Dec 12, 2024
@mistic @CAWilson94
skip flaky suite (elastic#203906)
67a0192
ashokaditya added a commit to ashokaditya/kibana that referenced this issue Dec 16, 2024
@ashokaditya
Update execute.ts
c3b4176 
closes elastic#203906
closes elastic#203897
ashokaditya added a commit to ashokaditya/kibana that referenced this issue Dec 16, 2024
@ashokaditya
Update execute.ts
810f312 
closes elastic#203906
closes elastic#203897
@ashokaditya ashokaditya mentioned this issue Dec 16, 2024
Merged
9 tasks
ashokaditya added a commit to ashokaditya/kibana that referenced this issue Dec 16, 2024
@ashokaditya
[SecuritySolution][Endpoint] Unskip ftr tests (elastic#204405)
f76f3f9 
## Summary

closes elastic#203909
closes elastic#203910
closes elastic#203908
closes elastic#203903
closes elastic#203906
closes elastic#203897
closes elastic#203893
closes elastic#203898

### Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

(cherry picked from commit 8f6e3ca)

# Conflicts:
#	x-pack/test/security_solution_api_integration/test_suites/edr_workflows/policy_response/trial_license_complete_tier/policy_response.ts
#	x-pack/test/security_solution_api_integration/test_suites/edr_workflows/response_actions/trial_license_complete_tier/execute.ts
#	x-pack/test/security_solution_api_integration/test_suites/edr_workflows/spaces/trial_license_complete_tier/space_awareness.ts
@kibanamachine kibanamachine reopened this Dec 18, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

JoseLuisGJ pushed a commit to JoseLuisGJ/kibana that referenced this issue Dec 19, 2024
@ashokaditya @JoseLuisGJ
[SecuritySolution][Endpoint] Unskip ftr tests (elastic#204405)
037d4c8 
## Summary

closes elastic#203909
closes elastic#203910
closes elastic#203908
closes elastic#203903
closes elastic#203906
closes elastic#203897
closes elastic#203893
closes elastic#203898

### Checklist

Check the PR satisfies following conditions. 

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Defend Workflows “EDR Workflows” sub-team of Security Solution
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[SecuritySolution][Endpoint] Unskip ftr tests ashokaditya/kibana
3 participants
@mistic @elasticmachine @kibanamachine