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

Failing test: Security Solution Cypress.x-pack/plugins/security_solution/public/management/cypress/e2e/response_actions/response_console/execute·cy·ts - Response console Execute operations: "before all" hook for ""execute --command" - should execute a command" "before all" hook for ""execute --command" - should execute a command" #170373

Open
kibanamachine opened this issue Nov 1, 2023 · 327 comments · Fixed by #173589, #179743, #181655, #186073 or #188013
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Defend Workflows “EDR Workflows” sub-team of Security Solution Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Nov 1, 2023

A test failed on a tracked branch

CypressError: `cy.task('indexFleetEndpointPolicy')` timed out after waiting `60000ms`.

https://on.cypress.io/api/task

Because this error occurred during a `before all` hook we are skipping the remaining tests in the current suite: `Execute operations:`

Although you have test retries enabled, we do not retry tests when `before all` or `after all` hooks fail
    at <unknown> (https://localhost:5651/__cypress/runner/cypress_runner.js:135256:70)
    at tryCatcher (https://localhost:5651/__cypress/runner/cypress_runner.js:1807:23)
    at <unknown> (https://localhost:5651/__cypress/runner/cypress_runner.js:4186:41)
    at tryCatcher (https://localhost:5651/__cypress/runner/cypress_runner.js:1807:23)
    at Promise._settlePromiseFromHandler (https://localhost:5651/__cypress/runner/cypress_runner.js:1519:31)
    at Promise._settlePromise (https://localhost:5651/__cypress/runner/cypress_runner.js:1576:18)
    at Promise._settlePromise0 (https://localhost:5651/__cypress/runner/cypress_runner.js:1621:10)
    at Promise._settlePromises (https://localhost:5651/__cypress/runner/cypress_runner.js:1697:18)
    at _drainQueueStep (https://localhost:5651/__cypress/runner/cypress_runner.js:2407:12)
    at _drainQueue (https://localhost:5651/__cypress/runner/cypress_runner.js:2400:9)
    at Async._drainQueues (https://localhost:5651/__cypress/runner/cypress_runner.js:2416:5)
    at Async.drainQueues (https://localhost:5651/__cypress/runner/cypress_runner.js:2286:14)
From Your Spec Code:
    at createAgentPolicyTask (webpack:///./tasks/fleet.ts:88:12)
    at Context.eval (webpack:///./e2e/response_actions/response_console/execute.cy.ts:38:30)

First failure: CI Build - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Nov 1, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 1, 2023
@kibanamachine kibanamachine added the Team:Defend Workflows “EDR Workflows” sub-team of Security Solution label Nov 1, 2023
@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 Nov 1, 2023
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@mistic
Copy link
Member

mistic commented Nov 3, 2023

Skipped.

main: 0cd75d9

@dasansol92
Copy link
Contributor

PR: #170001

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kevinlog
Copy link
Contributor

kevinlog commented Nov 9, 2023

@dasansol92 new error - looks to be serverless specific and getting a connection refused with the standalone Fleet Server

1) Response console
--
  | Execute operations:
  | "before all" hook for ""execute --command" - should execute a command":
  | CypressError: `cy.task('createEndpointHost')` failed with the following error:
  |  
  | > Command failed with exit code 1: vagrant ssh -- cd elastic-agent-8.12.0-SNAPSHOT-linux-x86_64 && sudo ./elastic-agent install --insecure --force --url https://10.128.0.248:8266 --enrollment-token OERhcXRJc0JVV2djMzVJYms0QjE6UDU5Z1ZzRUdReFdnMmYtU2szZzlMUQ==
  | {"log.level":"warn","@timestamp":"2023-11-09T15:26:27.848Z","log.logger":"tls","log.origin":{"file.name":"tlscommon/tls_config.go","file.line":107},"message":"SSL/TLS verifications disabled.","ecs.version":"1.6.0"}
  | {"log.level":"info","@timestamp":"2023-11-09T15:26:28.489Z","log.origin":{"file.name":"cmd/enroll_cmd.go","file.line":479},"message":"Starting enrollment to URL: https://10.128.0.248:8266/","ecs.version":"1.6.0"}
  | {"log.level":"warn","@timestamp":"2023-11-09T15:26:28.749Z","log.logger":"tls","log.origin":{"file.name":"tlscommon/tls_config.go","file.line":107},"message":"SSL/TLS verifications disabled.","ecs.version":"1.6.0"}
  | Error: fail to enroll: fail to execute request to fleet-server: dial tcp 10.128.0.248:8266: connect: connection refused
  | For help, please see our troubleshooting guide at https://www.elastic.co/guide/en/fleet/8.12/fleet-troubleshooting.html
  | Error: enroll command failed for unknown reason: exit status 1
  | For help, please see our troubleshooting guide at https://www.elastic.co/guide/en/fleet/8.12/fleet-troubleshooting.html
  |  
  | https://on.cypress.io/api/task
  |  
  | Because this error occurred during a `before all` hook we are skipping the remaining tests in the current suite: `Execute operations:`
  |  
  | Although you have test retries enabled, we do not retry tests when `before all` or `after all` hooks fail

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@MindyRS MindyRS added the Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. label Dec 14, 2023
@elasticmachine
Copy link
Contributor

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

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.14

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.14

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine kibanamachine reopened this Sep 2, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Defend Workflows “EDR Workflows” sub-team of Security Solution Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet