Skip to content

Operator test fails on cleanup #5886

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

Closed
jkhelil opened this issue Mar 19, 2025 · 2 comments
Closed

Operator test fails on cleanup #5886

jkhelil opened this issue Mar 19, 2025 · 2 comments

Comments

@jkhelil
Copy link
Contributor

jkhelil commented Mar 19, 2025

I am unable to reproduce the issue by testing with OLM locally, I also run the playbook locally but not getting the issue
this blocking PR #5728

TASK [cleanup_operator_resources : Delete the operator owned CRDs if any] ******
changed: [localhost] => (item=/tmp/operator-test/operator-files/manifests/operator.tekton.dev_tektonresults.yaml)
changed: [localhost] => (item=/tmp/operator-test/operator-files/manifests/operator.tekton.dev_tektontriggers.yaml)
changed: [localhost] => (item=/tmp/operator-test/operator-files/manifests/operator.tekton.dev_tektoninstallersets.yaml)
changed: [localhost] => (item=/tmp/operator-test/operator-files/manifests/operator.tekton.dev_tektondashboards.yaml)
changed: [localhost] => (item=/tmp/operator-test/operator-files/manifests/operator.tekton.dev_tektonhubs.yaml)
failed: [localhost] (item=/tmp/operator-test/operator-files/manifests/operator.tekton.dev_tektonconfigs.yaml) => changed=true 
  ansible_loop_var: owned_crd_path
  cmd: kubectl delete -f /tmp/operator-test/operator-files/manifests/operator.tekton.dev_tektonconfigs.yaml --ignore-not-found=true --timeout=300s
  delta: '0:05:00.050469'
  end: '2025-03-19 14:14:52.592564'
  msg: non-zero return code
  owned_crd_path: /tmp/operator-test/operator-files/manifests/operator.tekton.dev_tektonconfigs.yaml
  rc: 1
  start: '2025-03-19 14:09:52.542095'
  stderr: 'error: timed out waiting for the condition on customresourcedefinitions/tektonconfigs.operator.tekton.dev'
  stderr_lines: <omitted>
  stdout: customresourcedefinition.apiextensions.k8s.io "tektonconfigs.operator.tekton.dev" deleted
  stdout_lines: <omitted>
failed: [localhost] (item=/tmp/operator-test/operator-files/manifests/operator.tekton.dev_tektonpipelines.yaml) => changed=true 
  ansible_loop_var: owned_crd_path
  cmd: kubectl delete -f /tmp/operator-test/operator-files/manifests/operator.tekton.dev_tektonpipelines.yaml --ignore-not-found=true --timeout=300s
  delta: '0:05:00.050597'
  end: '2025-03-19 14:19:52.825758'
  msg: non-zero return code
  owned_crd_path: /tmp/operator-test/operator-files/manifests/operator.tekton.dev_tektonpipelines.yaml
  rc: 1
  start: '2025-03-19 14:14:52.775161'
  stderr: 'error: timed out waiting for the condition on customresourcedefinitions/tektonpipelines.operator.tekton.dev'
  stderr_lines: <omitted>
  stdout: customresourcedefinition.apiextensions.k8s.io "tektonpipelines.operator.tekton.dev" deleted
  stdout_lines: <omitted>
changed: [localhost] => (item=/tmp/operator-test/operator-files/manifests/operator.tekton.dev_manualapprovalgates.yaml)
failed: [localhost] (item=/tmp/operator-test/operator-files/manifests/operator.tekton.dev_tektonchains.yaml) => changed=true 
  ansible_loop_var: owned_crd_path
  cmd: kubectl delete -f /tmp/operator-test/operator-files/manifests/operator.tekton.dev_tektonchains.yaml --ignore-not-found=true --timeout=300s
  delta: '0:05:00.052925'
  end: '2025-03-19 14:24:53.395992'
  msg: non-zero return code
  owned_crd_path: /tmp/operator-test/operator-files/manifests/operator.tekton.dev_tektonchains.yaml
  rc: 1
  start: '2025-03-19 14:19:53.343067'
  stderr: 'error: timed out waiting for the condition on customresourcedefinitions/tektonchains.operator.tekton.dev'
  stderr_lines: <omitted>
  stdout: customresourcedefinition.apiextensions.k8s.io "tektonchains.operator.tekton.dev" deleted
  stdout_lines: <omitted>

Copy link
Contributor

This issue is stale because it has been open for 30 days with no activity.

Copy link
Contributor

This issue was closed because it has been inactive for 30 days since being marked as stale.

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

No branches or pull requests

1 participant