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

ImagePullBackOff for pruner #2368

Closed
tomalexander opened this issue Oct 1, 2024 · 2 comments
Closed

ImagePullBackOff for pruner #2368

tomalexander opened this issue Oct 1, 2024 · 2 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@tomalexander
Copy link

tomalexander commented Oct 1, 2024

Expected Behavior

The tekton pruner should run successfully

Actual Behavior

  containerStatuses:
  - image: gcr.io/tekton-releases/dogfooding/tkn:8d4383ff675cdf42b0006fca9b5b3b0c1d6180ff0013805242c877352e03a359
    imageID: ""
    lastState: {}
    name: tkn-pruner
    ready: false
    restartCount: 0
    started: false
    state:
      waiting:
        message: Back-off pulling image "gcr.io/tekton-releases/dogfooding/tkn:8d4383ff675cdf42b0006fca9b5b3b0c1d6180ff0013805242c877352e03a359"
        reason: ImagePullBackOff

Steps to Reproduce the Problem

  1. I installed tekton-operator-0.73.0
  2. Enabled the pruner with:
apiVersion: operator.tekton.dev/v1alpha1
kind: TektonConfig
metadata:
  name: config
spec:
  profile: all
  targetNamespace: tekton-pipelines
  pruner:
    resources:
      - pipelinerun
      - taskrun
    keep: ~
    keep-since: 86400
    schedule: "0,30 * * * *"
  1. The pruner fails to start.

But you can easily see this issue without installing tekton. First you can see the references to this specific container in the code base: https://github.com/search?q=org%3Atektoncd+8d4383ff675cdf42b0006fca9b5b3b0c1d6180ff0013805242c877352e03a359&type=code

And then you can try pulling said image:

$ docker pull 'gcr.io/tekton-releases/dogfooding/tkn:8d4383ff675cdf42b0006fca9b5b3b0c1d6180ff0013805242c877352e03a359'
Error response from daemon: manifest for gcr.io/tekton-releases/dogfooding/tkn:8d4383ff675cdf42b0006fca9b5b3b0c1d6180ff0013805242c877352e03a359 not found: manifest unknown: Failed to fetch "8d4383ff675cdf42b0006fca9b5b3b0c1d6180ff0013805242c877352e03a359" from request "/v2/tekton-releases/dogfooding/tkn/manifests/8d4383ff675cdf42b0006fca9b5b3b0c1d6180ff0013805242c877352e03a359".

Additional Info

  • Kubernetes version:
Client Version: v1.31.1
Kustomize Version: v5.4.2
Server Version: v1.30.2
  • Tekton Pipeline version:
v0.62.3
@tomalexander tomalexander added the kind/bug Categorizes issue or PR as related to a bug. label Oct 1, 2024
@jkandasa
Copy link
Member

jkandasa commented Oct 2, 2024

@tomalexander thanks to reporting this back. I will update this soon as possible.
till then can you please update the IMAGE_JOB_PRUNER_TKN environment variable as workaround?
https://github.com/tektoncd/operator/blob/main/docs/AirGapImageConfiguration.md

@jkandasa jkandasa self-assigned this Oct 2, 2024
@jkandasa
Copy link
Member

jkandasa commented Oct 9, 2024

@jkandasa jkandasa closed this as completed Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants