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/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/related_integrations/related_integrations·cy·ts - Related integrations related Integrations Advanced Setting is disabled rules management table "before each" hook for "should not display a badge with the installed integrations" "before each" hook for "should not display a badge with the installed integrations" #176028

Closed
Tracked by #173731
kibanamachine opened this issue Feb 1, 2024 · 5 comments
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Related Integrations Security Solution Detection Rules Related Integrations feature Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@kibanamachine
Copy link
Contributor

A test failed on a tracked branch

CypressError: `cy.request()` failed on:

http://localhost:5687/api/fleet/epm/packages

The response we received from your web server was:

  > 500: Internal Server Error

This was considered a failure because the status code was not `2xx` or `3xx`.

If you do not want status codes to cause failures pass the option: `failOnStatusCode: false`

-----------------------------------------------------------

The request we sent was:

Method: GET
URL: http://localhost:5687/api/fleet/epm/packages
Headers: {
  "Connection": "keep-alive",
  "kbn-xsrf": "cypress-creds",
  "x-elastic-internal-origin": "security-solution",
  "elastic-api-version": [
    "2023-10-31"
  ],
  "user-agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Cypress/13.3.0 Chrome/114.0.5735.289 Electron/25.8.1 Safari/537.36",
  "accept": "*/*",
  "cookie": "sid=Fe26.2**63e338649dc634914d53ac088759398d3256e99a7670e81f13aced11974701ec*sjajmmtgUgKbyO_YcMYfPA*F2tYGDlRokrHxsRupAxyLXsIh1YrG0K8zeSYCYga7LznE7NsfHRw1Xan72wGoQ5oa0eGZ6vtHwi7GcC8heGgWUJlBpvhZSBH-WXE9kwHMdV_W3rTQW_3wRyBbKaB35lxr3ArLRGnNaT1lgomm7kZFL3fnVL4LNG1wcjcCj6CHvx5QkMwZwy5MZAw3cwT66P8aT7DfMqymrYXg3llQDsAWc4UtGfcm_RASMEXa7_pBzuai2B_KCyjJmbWfVKrlmiW**a88a97ba71988a07b5eb8366c299fb61262eb5c07d3e39dcaff41bbd5324b210*ghn9E2rHM_q9ultaTCeZsuWdGW55eBEul634a3_KQVg",
  "authorization": "Basic c3lzdGVtX2luZGljZXNfc3VwZXJ1c2VyOmNoYW5nZW1l",
  "accept-encoding": "gzip, deflate"
}

-----------------------------------------------------------

The response we got was:

Status: 500 - Internal Server Error
Headers: {
  "elastic-api-version": "2023-10-31",
  "strict-transport-security": "max-age=31536000; includeSubDomains",
  "x-content-type-options": "nosniff",
  "referrer-policy": "no-referrer-when-downgrade",
  "permissions-policy": "camera=(), display-capture=(), fullscreen=(self), geolocation=(), microphone=(), web-share=()",
  "cross-origin-opener-policy": "same-origin",
  "x-frame-options": "SAMEORIGIN",
  "content-security-policy": "script-src 'report-sample' 'self'; worker-src 'report-sample' 'self' blob:; style-src 'report-sample' 'self' 'unsafe-inline'; frame-ancestors 'self'",
  "kbn-name": "kb-n2-4-spot-56740dc975f7f430",
  "kbn-license-sig": "2653816f9bf7ba166feb00a0152aa5fea11e981d9b101bb229a115375180a335",
  "content-type": "application/json; charset=utf-8",
  "cache-control": "private, no-cache, no-store, must-revalidate",
  "content-length": "196",
  "date": "Wed, 31 Jan 2024 23:56:01 GMT",
  "connection": "keep-alive",
  "keep-alive": "timeout=120"
}
Body: {
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "'403 Forbidden' error response from package registry at https://epr.elastic.co/search?capabilities=security&spec.min=1.0&spec.max=3.0"
}


https://on.cypress.io/request

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `Related integrations`
    at <unknown> (http://localhost:5687/__cypress/runner/cypress_runner.js:133043:72)
    at tryCatcher (http://localhost:5687/__cypress/runner/cypress_runner.js:1807:23)
    at Promise._settlePromiseFromHandler (http://localhost:5687/__cypress/runner/cypress_runner.js:1519:31)
    at Promise._settlePromise (http://localhost:5687/__cypress/runner/cypress_runner.js:1576:18)
    at Promise._settlePromise0 (http://localhost:5687/__cypress/runner/cypress_runner.js:1621:10)
    at Promise._settlePromises (http://localhost:5687/__cypress/runner/cypress_runner.js:1701:18)
    at _drainQueueStep (http://localhost:5687/__cypress/runner/cypress_runner.js:2407:12)
    at _drainQueue (http://localhost:5687/__cypress/runner/cypress_runner.js:2400:9)
    at Async._drainQueues (http://localhost:5687/__cypress/runner/cypress_runner.js:2416:5)
    at Async.drainQueues (http://localhost:5687/__cypress/runner/cypress_runner.js:2286:14)
From Your Spec Code:
    at rootRequest (webpack:///./tasks/api_calls/common.ts:29:5)
    at deletePackages (webpack:///./tasks/api_calls/fleet.ts:57:90)
    at Context.eval (webpack:///./tasks/api_calls/fleet.ts:17:6)

First failure: CI Build - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Feb 1, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Feb 1, 2024
@kibanamachine kibanamachine added the Team:Detection Rule Management Security Detection Rule Management Team label Feb 1, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Feb 1, 2024
@banderror banderror added Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Feature:Related Integrations Security Solution Detection Rules Related Integrations feature labels Feb 1, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Contributor

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

@banderror
Copy link
Contributor

So the 500 error happened in the /api/fleet/epm/packages endpoint which in turn received an error response from EPR:

'403 Forbidden' error response from package registry at https://epr.elastic.co/search?capabilities=security&spec.min=1.0&spec.max=3.0

My guess is that it's not a legit flake, and the error happened because EPR wasn't fully available / initialized. Maybe it was restarting at this moment.

I'm not skipping this test. I will keep the ticket in the backlog for a few days, and if the flake doesn't reoccur, I'll close it.

@banderror
Copy link
Contributor

The flake didn't reoccur, closing the ticket.

@banderror banderror closed this as not planned Won't fix, can't repro, duplicate, stale Feb 7, 2024
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 Feature:Related Integrations Security Solution Detection Rules Related Integrations feature Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Development

No branches or pull requests

3 participants