tekton-kueue update

[rh-tap-build-team]

Included PRs:

• chore(deps): update konflux references konflux-ci/tekton-kueue#260

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rh-tap-build-team[bot]
Once this PR has been reviewed and has the lgtm label, please assign filariow for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• components/kueue/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

🤖 Gemini AI Assistant Available

Hi @rh-tap-build-team[bot]! I'm here to help with your pull request. You can interact with me using the following commands:

Available Commands

• @gemini-cli /review - Request a comprehensive code review

  • Example: @gemini-cli /review Please focus on security and performance

• @gemini-cli <your question> - Ask me anything about the codebase

  • Example: @gemini-cli How can I improve this function?
  • Example: @gemini-cli What are the best practices for error handling here?

How to Use

1. Simply type one of the commands above in a comment on this PR
2. I'll analyze your code and provide detailed feedback
3. You can track my progress in the workflow logs

Permissions

Only OWNER, MEMBER, or COLLABORATOR users can trigger my responses. This ensures secure and appropriate usage.

---

This message was automatically added to help you get started with the Gemini AI assistant. Feel free to delete this comment if you don't need assistance.

[github-actions]

🤖 Hi @rh-tap-build-team[bot], I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Timeout

The Prow job timed out because the e2e tests failed to apply Kubernetes manifests due to a file existence error during Helm chart extraction.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step failed due to a timeout after exceeding the 2-hour limit. The immediate cause was an error encountered by kustomize when trying to build manifests that involved Helm charts. The specific error reported was: "Error: Error: failed to untar: a file or directory with the name /components/vector-kubearchive-log-collector/development/charts/loki-6.49.0/loki-6.49.0.tgz already exists". This indicates a problem with Helm's ability to extract the chart into the specified directory.

Contributing Factors

While the primary failure was a timeout during manifest application, other contextual information points to potential underlying issues. Several ApplicationSet resources, such as multi-platform-controller and pipeline-service, are reported as OutOfSync. Additionally, the tekton-config resource has a ComponentsReady status of False with a message indicating that TektonAddon requires reconciliation. The tekton-addon itself shows InstallerSetReady and Ready conditions as False, citing "openshift console resources not yet ready" and a non-ready tkn-cli-serve deployment. These factors suggest that the environment or some of its core components might not be in an optimal state, potentially contributing to the manifest application issues.

Impact

The failure to apply Kubernetes manifests due to the Helm chart untar error directly caused the appstudio-e2e-tests step to time out. This timeout prevented the e2e tests from executing and completing, thereby blocking the overall Prow job and preventing any artifacts from being successfully generated or validated for the PR.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The e2e tests failed to complete within the allocated time, likely due to persistent errors in applying Kubernetes manifests via kustomize and helm, leading to a timeout of the main process. The specific error relates to a file already existing when trying to untar a helm chart.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.log line 1234

'kustomize build <path to cached source>/components/vector-kubearchive-log-collector/development --enable-helm ... ' failed exit status 1: Error: Error: failed to untar: a file or directory with the name <path to cached source>/components/vector-kubearchive-log-collector/development/charts/loki-6.49.0/loki-6.49.0.tgz already exists
: unable to run: 'helm pull --untar --untardir <path to cached source>/components/vector-kubearchive-log-collector/development/charts/loki-6.49.0 --repo https://grafana.github.io/helm-charts loki --version 6.49.0' with env=[HELM_CONFIG_HOME=/tmp/kustomize-helm-2346738319/helm HELM_CACHE_HOME=/tmp/kustomize-helm-2346738319/helm/.cache HELM_DATA_HOME=/tmp/kustomize-helm-2346738319/helm/.data] (is 'helm' installed?): exit status 1

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.log line 1589

{"component":"entrypoint","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:169","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.ExecuteProcess","level":"error","msg":"Process did not finish before 2h0m0s timeout","severity":"error","time":"2026-01-31T15:15:17Z"}

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.log line 1592

{"component":"entrypoint","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:267","func":"sigs.k8s.io/prow/pkg/entrypoint.gracefullyTerminate","level":"error","msg":"Process did not exit before 15s grace period","severity":"error","time":"2026-01-31T15:15:32Z"}

---

Analysis powered by prow-failure-analysis | Build: 2017584449889243136

[openshift-ci]

@rh-tap-build-team[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/appstudio-e2e-tests	19dd16d	link	true	/test appstudio-e2e-tests

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.