Project

General

Profile

Actions

Bug #58722

closed

cephadm dashboard e2e failures

Added by Nizamudeen A over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Build, CI, Dependencies & Tools
Target version:
-
% Done:

0%

Source:
Tags:
backport_processed
Backport:
quincy, pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

HttpErrorResponse: The following error originated from your application code, not from Cypress.

> Http failure response for https://192.168.100.100:8443/api/prometheus/rules: 400 Bad Request

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Description of problem

here

Environment

  • ceph version string:
  • Platform (OS/distro/release):
  • Cluster details (nodes, monitors, OSDs):
  • Did it happen on a stable environment or after a migration/upgrade?:
  • Browser used (e.g.: Version 86.0.4240.198 (Official Build) (64-bit)):

How reproducible

Steps:

  1. ...

Actual results

Please add logs and/or screenshots

Expected results

here

Additional info

here


Related issues 2 (0 open2 closed)

Copied to Dashboard - Backport #58741: quincy: cephadm dashboard e2e failuresResolvedNizamudeen AActions
Copied to Dashboard - Backport #59347: pacific: cephadm dashboard e2e failuresResolvedNizamudeen AActions
Actions

Also available in: Atom PDF