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

autoscale E2E test doesn't pass in OpenShift #1364

Closed
iblancasa opened this issue Jan 12, 2023 · 0 comments · Fixed by #1365
Closed

autoscale E2E test doesn't pass in OpenShift #1364

iblancasa opened this issue Jan 12, 2023 · 0 comments · Fixed by #1365

Comments

@iblancasa
Copy link
Contributor

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

  1. Create an OpenShift cluster (4.11 in my case)
  2. Build and deploy the OpenTelemetry Collector Operator
  3. 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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant