Actions
Bug #58722
closedcephadm dashboard e2e failures
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:
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:
- ...
Actual results¶
Please add logs and/or screenshots
Expected results¶
here
Additional info¶
here
Updated by Nizamudeen A about 1 year ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot about 1 year ago
- Copied to Backport #58741: quincy: cephadm dashboard e2e failures added
Updated by Nizamudeen A about 1 year ago
- Status changed from Pending Backport to Resolved
Updated by Nizamudeen A about 1 year ago
- Status changed from Resolved to Pending Backport
- Tags deleted (
backport_processed) - Backport changed from quincy to quincy, pacific
Updated by Backport Bot about 1 year ago
- Copied to Backport #59347: pacific: cephadm dashboard e2e failures added
Updated by Nizamudeen A about 1 year ago
- Status changed from Pending Backport to Resolved
Actions