Update pipelines-index-4.17 to next nightly build in dev/staging 5.0.5-771

[infernus01]

Update CatalogSource image to latest nightly build: sha256:4f294280ec01d2e3f9f5ac40488c1c0db30c0b9ee9aeec664ec2853cf8a53932

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: infernus01
Once this PR has been reviewed and has the lgtm label, please assign enarha 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/pipeline-service/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 @infernus01! 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 @infernus01, 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

Pipeline failed due to a timeout in end-to-end tests, likely caused by widespread Argo CD application synchronization issues.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step timed out after exceeding the 2-hour execution limit.

Contributing Factors

Analysis of additional_context reveals that numerous Argo CD ApplicationSets are in an OutOfSync state, with their corresponding Applications marked as Missing in terms of health status. This widespread synchronization problem indicates a potential failure in the continuous deployment process, which could be consuming cluster resources or causing delays that prevent the E2E tests from completing within their allocated time.

Impact

The timeout of the end-to-end tests prevented the successful completion of the Prow job, blocking the integration and validation of infrastructure deployments for AppStudio. This failure means that any potential issues or regressions in the deployed infrastructure were not detected by the automated E2E test suite.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The end-to-end tests exceeded the maximum allowed execution time, leading to a timeout failure. This could be due to test flakiness, performance degradation, or an actual issue within the application being tested that causes prolonged test execution.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step-log.txt line 1324

{"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-02T20:14:25Z"}

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step-log.txt line 1326

{"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-02T20:14:40Z"}

---

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

[aThorp96]

@infernus01 FYI I think there might be an issue with the upstream images included here; it looks like PaC is on the same version

$ osp-index-info compare  quay.io/openshift-pipeline/pipelines-index-4.17@sha256:da69014f19f4d6f07564659b7233b9359065df6d090457b6c36d3e699a059b79 quay.io/openshift-pipeline/pipelines-index-4.17@sha256:4f294280ec01d2e3f9f5ac40488c1c0db30c0b9ee9aeec664ec2853cf8a53932 show-heads
Comparing quay.io/openshift-pipeline/pipelines-index-4.17@sha256:da69014f19f4d6f07564659b7233b9359065df6d090457b6c36d3e699a059b79 to quay.io/openshift-pipeline/pipelines-index-4.17@sha256:4f294280ec01d2e3f9f5ac40488c1c0db30c0b9ee9aeec664ec2853cf8a53932 for v5.0.5
---
tektoncd/pipeline:
        old commit: 478d30f0a799663216cd225cf826e0b1efdadee3
        new commit: 478d30f0a799663216cd225cf826e0b1efdadee3
openshift-pipelines/pipelines-as-code:
        old commit: 3c453676968454dd6a72f987b19a9946f6aa3327
        new commit: 3c453676968454dd6a72f987b19a9946f6aa3327
tektoncd/cli:
        old commit: 994290b9fd881d301f851ffcadcde0fb6e935419
        new commit: 994290b9fd881d301f851ffcadcde0fb6e935419
tektoncd/results:
        old commit: f0837abc7d3d5051a48e68eb21adac7769660657
        new commit: f0837abc7d3d5051a48e68eb21adac7769660657
tektoncd/operator:
        old commit: 2fa1b3c0a0d8e7386cfdc936fc22685176096124
        new commit: 6cbd178e2a639c1fc612da9868f2ec5dff2379c9
tektoncd/hub:
        old commit: d10d0fd4aa8ce60583f6978516f45b74d4a80603
        new commit: d10d0fd4aa8ce60583f6978516f45b74d4a80603
openshift-pipelines/tekton-caches:
        old commit: d374099aedd0152a43d59eb6948b4c83a9406a51
        new commit: d374099aedd0152a43d59eb6948b4c83a9406a51
openshift-pipelines/manual-approval-gate:
        old commit: ac0d2c063bc84d1ab28c1a3cae27aba3ae1adb6b
        new commit: e5f78d7e3856231d2b13a6eaf82532c1e4648cbd
openshift-pipelines/tektoncd-git-clone:
        old commit: 768a778f1f7ccee8a4dd142e7f115e12c7e422fd
        new commit: 768a778f1f7ccee8a4dd142e7f115e12c7e422fd
tektoncd/triggers:
        old commit: 66a7b7d78178f2388fe1b11e44c54105b0be5785
        new commit: 76660c5e6df0c1de79fee34a9d71911d51095129
tektoncd/chains:
        old commit: 0c9284f740d672930274efbe75033df55dc78515
        new commit: 0c9284f740d672930274efbe75033df55dc78515
tektoncd/pruner:
        old commit: 3435793eaddf70264200520f00c9ce70aeb8fa30
        new commit: 7b7814fce640d5b1b1f930fa3da7ccb39e9868d9```

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Unknown

The E2E test job failed because the analysis step encountered a context window error when processing large amounts of data, preventing the successful execution and reporting of test results.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step failed with a litellm.ContextWindowExceededError. This error occurred because the input provided to the language model for analysis exceeded its maximum token limit.

Contributing Factors

Several E2E tests also failed with the same litellm.ContextWindowExceededError. Additionally, numerous appstudio-e2e-tests/redhat-appstudio-gather/artifacts/ analyses failed with JSON parsing errors ("Expecting ',' delimiter"), indicating a potential systemic issue with artifact collection, serialization, or the volume of data being processed by the analysis tools. One test also failed due to container image preflight check failures, which is a secondary failure mode.

Impact

The failure in the analysis step prevented the E2E tests from completing and producing actionable results. The context window error suggests that the volume of data being generated or analyzed by the E2E test suite is too large for the current tooling, or that there is an issue with how this data is being handled. This directly blocked the validation of the App Studio infra deployments.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: unknown
Root Cause: Analysis failed: litellm.ContextWindowExceededError: litellm.BadRequestError: ContextWindowExceededError: GeminiException - {
"error": {
"code": 400,
"message": "The input token count exceeds the maximum number of tokens allowed (1048576).",
"status": "INVALID_ARGUMENT"
}
}

---

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

[openshift-ci]

@infernus01: 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	b8e3560	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.

[infernus01]

/hold