Test elastic-package#1464 - DO NOT MERGE

[elasticmachine]

Update elastic-package reference to elastic/elastic-package@7d24209.
Automated by Buildkite build

Relates: elastic/elastic-package#1464

[elasticmachine]

💔 Tests Failed

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: 2023-09-21T14:33:19.725+0000

• Duration: 363 min 4 sec

Test stats 🧪

Test	Results
Failed	23
Passed	4558
Skipped	8
Total	4589

Test errors

Expand to view the tests failures

> Show only the first 10 test failures

Check integrations / hashicorp_vault / hashicorp_vault: check / static test: Verify sample_event.json – hashicorp_vault.audit

Expand to view the error details

 null 

Expand to view the stacktrace

 one or more errors found in document: [0] parsing field value failed: field "event.type" value "change" is not one of the expected values (start, end, info) for any of the values of "event.category" (authentication) 

Check integrations / proofpoint_tap / proofpoint_tap: check / pipeline test: test-clicks-blocked.log – proofpoint_tap.clicks_blocked

Expand to view the error details

 null 

Expand to view the stacktrace

 test case failed: one or more problems with fields found in documents: [0] parsing field value failed: field "event.type" value "denied" is not one of the expected values (info) for any of the values of "event.category" (email) 

Check integrations / proofpoint_tap / proofpoint_tap: check / pipeline test: test-clicks-permitted.log – proofpoint_tap.clicks_permitted

Expand to view the error details

 null 

Expand to view the stacktrace

 test case failed: one or more problems with fields found in documents: [0] parsing field value failed: field "event.type" value "allowed" is not one of the expected values (info) for any of the values of "event.category" (email) 

Check integrations / proofpoint_tap / proofpoint_tap: check / pipeline test: test-message-blocked.log – proofpoint_tap.message_blocked

Expand to view the error details

 null 

Expand to view the stacktrace

 test case failed: one or more problems with fields found in documents: [0] parsing field value failed: field "event.type" value "denied" is not one of the expected values (info) for any of the values of "event.category" (email) 

Check integrations / ping_one / ping_one: check / static test: Verify sample_event.json – ping_one.audit

Expand to view the error details

 null 

Expand to view the stacktrace

 one or more errors found in document: [0] parsing field value failed: field "event.type" value "allowed" is not one of the expected values (admin, change, creation, deletion, group, info, user, access) for any of the values of "event.category" (iam, configuration) 

Check integrations / microsoft_defender_endpoint / microsoft_defender_endpoint: check / static test: Verify sample_event.json – microsoft_defender_endpoint.log

Expand to view the error details

 null 

Expand to view the stacktrace

 one or more errors found in document: [0] parsing field value failed: field "event.type" value "user" is not one of the expected values (access, change, end, info, start) for any of the values of "event.category" (host) 

Check integrations / ti_rapid7_threat_command / ti_rapid7_threat_command: check / static test: Verify sample_event.json – ti_rapid7_threat_command.vulnerability

Expand to view the error details

 null 

Expand to view the stacktrace

 one or more errors found in document: [0] parsing field value failed: field "event.type" value "info" is not one of the expected values (indicator) for any of the values of "event.category" (threat) 

Check integrations / slack / slack: check / pipeline test: test-audit.log – slack.audit

Expand to view the error details

 null 

Expand to view the stacktrace

 test case failed: one or more problems with fields found in documents: [0] parsing field value failed: field "event.type" value "allowed" is not one of the expected values (access, change, creation, deletion, info) for any of the values of "event.category" (file) 

Check integrations / tenable_sc / tenable_sc: check / pipeline test: test-vulnerability.log – tenable_sc.vulnerability

Expand to view the error details

 null 

Expand to view the stacktrace

 test case failed: one or more problems with fields found in documents: [0] parsing field value failed: field "event.type" value "info" is not one of the expected values (indicator) for any of the values of "event.category" (threat) 

Check integrations / keycloak / keycloak: check / pipeline test: test-log.log – keycloak.log

Expand to view the error details

 null 

Expand to view the stacktrace

 test case failed: one or more problems with fields found in documents: [0] parsing field value failed: field "event.type" value "allowed" is not one of the expected values (start, end, info) for any of the values of "event.category" (authentication)
[1] parsing field value failed: field "event.type" value "denied" is not one of the expected values (start, end, info) for any of the values of "event.category" (authentication) 

Steps errors

Expand to view the steps failures

Show only the first 10 steps failures

Update the Elastic stack

• Took 1 min 33 sec . View more details here
• Description: ../../build/elastic-package stack update -v --version 8.10.0

Test integration: pfsense

• Took 1 min 36 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: ping_one

• Took 0 min 17 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: prometheus_input

• Took 12 min 40 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: proofpoint_tap

• Took 0 min 24 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: slack

• Took 0 min 22 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: tenable_sc

• Took 0 min 24 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: ti_rapid7_threat_command

• Took 0 min 18 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: websphere_application_server

• Took 12 min 42 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Google Storage Download

• Took 0 min 0 sec . View more details here

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.