You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In one of the test cases - rest_apis/test_import_metadata.py::test_repeated_metadata_import_without_datasource_connection
we scale down prometheus deployment and replicaset to bring down datasource connection, but due to mismatch in status code and response message for POST /dsmetadata API, assertion error is thrown and prometheus connection is not restored leading to failures in subsequent tests.
Excepted response:
{
"message": "Metadata cannot be imported, datasource connection refused or timed out",
"httpcode": 400,
"documentationLink": "",
"status": "ERROR"
}
Current response:
Importing the metadata...
URL = http://kruize-openshift-tuning.apps.bm.example.com/dsmetadata
Response status code = 500
{
"message": "Internal Server Error: Connect to prometheus-k8s.openshift-monitoring.svc.cluster.local:9091 [prometheus-k8s.openshift-monitoring.svc.cluster.local/172.30.30.25] failed: Connection refused",
"httpcode": 500,
"documentationLink": "",
"status": "ERROR"
}
How to reproduce it
Run the functional tests from local monitoring test suite
Expected behavior
Validation of the expected error message and scaling back the prometheus deployment and statefulset to restore the datasource connection
Relevant logs
************************************************************
Deployment prometheus-operator scaled to 0 replicas successfully.
Deployment prometheus-adapter scaled to 0 replicas successfully.
StatefulSet prometheus-k8s scaled to 0 replicas successfully.
************************************************************
{
"version": "v1.0",
"datasource_name": "prometheus-1"
}
************************************************************
Importing the metadata...
URL = http://kruize-openshift-tuning.apps.bm.example.com/dsmetadata
Response status code = 500
{
"message": "Internal Server Error: Connect to prometheus-k8s.openshift-monitoring.svc.cluster.local:9091 [prometheus-k8s.openshift-monitoring.svc.cluster.local/172.30.30.25] failed: Connection refused",
"httpcode": 500,
"documentationLink": "",
"status": "ERROR"
}
Environment:
Kubernetes Cluster - Openshift
Version
OS
Additional context
.
The text was updated successfully, but these errors were encountered:
Describe the bug
Kruize local monitoring functional tests are failing due to datasource connection refused error with the latest build of Kruize 0.2
Local monitoring functional tests on Kruize Scalelab - https://ci.app-svc-perf.corp.redhat.com/job/ExternalTeams/job/Autotune/job/kruize_local_release_tests/10/#showFailuresLink
In one of the test cases -
rest_apis/test_import_metadata.py::test_repeated_metadata_import_without_datasource_connection
we scale down prometheus deployment and replicaset to bring down datasource connection, but due to mismatch in status code and response message for POST /dsmetadata API, assertion error is thrown and prometheus connection is not restored leading to failures in subsequent tests.
Excepted response:
Current response:
How to reproduce it
Run the functional tests from local monitoring test suite
Expected behavior
Validation of the expected error message and scaling back the prometheus deployment and statefulset to restore the datasource connection
Relevant logs
Environment:
Additional context
.
The text was updated successfully, but these errors were encountered: