Override tkn-cli-srv image

[aThorp96]

The previous image, quay.io/openshift-pipeline/pipelines-serve-tkn-cli-rhel9@sha256:ac27f336d3e4e9e2538a867c1a956ca8328428948dd72d9ad6456c346ab48989 seems to have disappeared from quay.io. While we investigate the issue and rollout the next release, this should get CI working again by overriding the image to a more recent version. Since tkn-cli-serve is unused by Konflux, this just needs to exist so the deployment can succeed

[github-actions]

🤖 Gemini AI Assistant Available

Hi @aThorp96! 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 @aThorp96, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[infernus01]

/lgtm

[infernus01]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aThorp96, infernus01

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• components/pipeline-service/OWNERS [aThorp96]

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

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Timeout

The E2E tests timed out due to prolonged application deployment and synchronization processes, potentially exacerbated by underlying Argo CD ApplicationSet synchronization issues and Tekton component errors.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step failed because the E2E tests exceeded the 2-hour execution timeout. The process was terminated after a grace period, indicating that the underlying operations did not complete within the expected timeframe.

Contributing Factors

Several factors may have contributed to the prolonged execution:

• Argo CD ApplicationSet Synchronization Issues: Artifacts show that several Argo CD ApplicationSets (build-service, cert-manager, etc.) are in an 'OutOfSync' state with a 'Missing' health status. This indicates that the desired application state is not being achieved, which could lead to deployment delays or failures.
• Tekton Component Errors: The tektonaddons and tektonconfigs resources are in an 'Error' state, with specific messages indicating that components like tkn-cli-serve are not ready. This could impact the functionality of the CI/CD pipeline, including deployment and testing processes.
• Potential for long-running deployments: The E2E tests rely on the successful deployment and synchronization of applications managed by Argo CD. If these deployments are inherently slow or encountering issues, they can easily exceed time limits.

Impact

The timeout prevented the completion of the E2E tests, meaning the pipeline could not validate the functionality and stability of the deployed application infrastructure. This failure blocks the main branch integration and deployment verification.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The E2E tests failed due to a timeout. This was likely caused by a prolonged execution of the application deployment and synchronization processes managed by Argo CD, which failed to complete within the allocated time limit.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt:2718

{"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-02-02T15:22:19Z"}

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt:2723

{"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-02-02T15:22:34Z"}

---

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

[aThorp96]

/retest

[openshift-ci]

New changes are detected. LGTM label has been removed.

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Timeout

Pipeline job failed due to the end-to-end tests exceeding the allocated timeout.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step failed because the test execution exceeded the configured 2-hour timeout. The process did not terminate within the expected timeframe and also failed to exit within the subsequent 15-second grace period.

Contributing Factors

While no specific test failures were reported, the additional_context reveals several ArgoCD ApplicationSets in an OutOfSync state and Tekton-related components (TektonAddon, TektonConfig) in an error state. These underlying cluster or deployment issues might have contributed to a slower-than-expected test execution or resource contention, indirectly leading to the timeout.

Impact

The timeout failure prevented the completion of the end-to-end test suite for this pull request, meaning the quality and correctness of the infrastructure changes could not be validated. This blocked the progression of the CI/CD pipeline for the affected changes.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The end-to-end tests exceeded the allocated timeout of 2 hours, and the process failed to terminate gracefully, indicating a potential deadlock or an excessively long-running test case.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt:1098

{"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-02-02T22:57:46Z"}

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt:1103

{"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-02-02T22:58:01Z"}

---

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

[openshift-ci]

@aThorp96: 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	a198c5c	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.