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
The autoscale E2E is failing when is runnned in an OpenShift cluster.
The test creates two OpenTelemetry Collectors. Each one deploys one Horizontal Pod Autoscaler:
$ kubectl get pods
NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE
simplest-collector OpenTelemetryCollector/simplest 0%/90% 1 2 1 10m
simplest-set-utilization-collector OpenTelemetryCollector/simplest-set-utilization 0%/50% 1 2 1 10m
Later, it tries to match them with the CRs from tests/e2e/autoscale/00-assert.yaml. Those CRs check for HPAs whose apiVersion are autoscaling/v1 (simplest-collector) and autoscaling/v2beta2 (simplest-set-utilization-collector). In OpenShift (4.11) both are created with an apiVersion with the value autoscaling/v2.
Steps to reproduce
Create an OpenShift cluster (4.11 in my case)
Build and deploy the OpenTelemetry Collector Operator
Run the autoscale E2E test ($ kuttl test --test autoscale)
Also, the test can be flaky since it always waits for a fixed CPU % utilization (that cannot be reached depending on the resources of the machine where the tests are running).
The text was updated successfully, but these errors were encountered:
The
autoscale
E2E is failing when is runnned in an OpenShift cluster.The test creates two OpenTelemetry Collectors. Each one deploys one Horizontal Pod Autoscaler:
Later, it tries to match them with the CRs from
tests/e2e/autoscale/00-assert.yaml
. Those CRs check for HPAs whoseapiVersion
areautoscaling/v1
(simplest-collector
) andautoscaling/v2beta2
(simplest-set-utilization-collector
). In OpenShift (4.11) both are created with anapiVersion
with the valueautoscaling/v2
.Steps to reproduce
autoscale
E2E test ($ kuttl test --test autoscale
)Also, the test can be flaky since it always waits for a fixed CPU % utilization (that cannot be reached depending on the resources of the machine where the tests are running).
The text was updated successfully, but these errors were encountered: