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

Jobs don't start #513

Open
kotyara85 opened this issue Dec 21, 2024 · 1 comment
Open

Jobs don't start #513

kotyara85 opened this issue Dec 21, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@kotyara85
Copy link

kotyara85 commented Dec 21, 2024

Brief summary

Hello everyone,
Here's my test config:

Only one pod is created and the operator is complaining on this -

2024-12-21T20:22:48Z	ERROR	Reconciler error	{"controller": "testrun", "controllerGroup": "k6.io", "controllerKind": "TestRun", "TestRun": {"name":"test","namespace":"k6"}, "namespace": "k6", "name": "test", "reconcileID": "0ea50705-3aea-4613-8350-39fa2161c3e4", "error": "job with the name test-1 exists; make sure you've deleted your previous run"}

I did delete all previous jobs before starting the test. Any help is appreciated

k6-operator version or image

v0.0.18

Helm chart version (if applicable)

No response

TestRun / PrivateLoadZone YAML

apiVersion: k6.io/v1alpha1
kind: TestRun
metadata:
  name: test
  namespace: k6
spec:
  parallelism: 100
  script:
    configMap:
      name: test
      file: script.js
  runner:
    resources:
      requests:
        cpu: 100m
        memory: "128Mi"
      limits:
        cpu: "12"
        memory: 16Gi
    image: ghcr.io/grafana/k6-operator:latest-runner
  starter:
    resources:
      requests:
        cpu: 100m
        memory: "128Mi"
      limits:
        cpu: "12"
        memory: 16Gi
    image: ghcr.io/grafana/k6-operator:latest-starter
  arguments: --verbose

Other environment details (if applicable)

No response

Steps to reproduce the problem

Install operator
Try to run tests

Expected behaviour

Tests to run

Actual behaviour

Tests do not start

@kotyara85 kotyara85 added the bug Something isn't working label Dec 21, 2024
@yorugac
Copy link
Collaborator

yorugac commented Jan 2, 2025

Hi @kotyara85, sorry for the delay; it's been a holiday season. Without reproducible steps, this case is hard to classify as a bug from the operator's side. Clearly, there is something additional in your setup that causes this behaviour. I think it makes sense to check the logs of k6-operator app itself: was there any error upon deletion attempt there? Additionally, what do the usual kubectl commands say? Specifically, kubectl get testrun and kubectl delete testrun?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants