caching update

[rh-tap-build-team]

Included PRs:

• chore(deps): update registry.access.redhat.com/ubi10/nginx-126 docker digest to f51afbf konflux-ci/caching#601
• chore(deps): update registry.fedoraproject.org/fedora:latest docker digest to 966cfb6 konflux-ci/caching#603

[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 yftacherzog 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/squid/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 end-to-end tests timed out due to a degraded state of the build-service-in-cluster-local application, likely caused by underlying Tekton component readiness issues.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step failed with a timeout. This timeout is attributed to the build-service-in-cluster-local application being in a prolonged degraded state.

Contributing Factors

Analysis of the provided artifacts reveals that the build-service-in-cluster-local component is in a 'Progressing' state within its ApplicationSet, and another related component, application-api-in-cluster-local, is in an 'OutOfSync' state. Furthermore, Tekton configurations indicate that Tekton Addon reconciliation is failing, and the tkn-cli-serve deployment is not ready. These issues collectively suggest an unstable or incomplete deployment of core AppStudio infrastructure components, impacting the build service's functionality.

Impact

The degraded state of the build service and related infrastructure components prevented the end-to-end tests from completing within their allocated time. This blocked the successful execution and validation of the AppStudio deployments for the given pull request.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The end-to-end tests timed out, likely due to the prolonged degraded state of the build-service-in-cluster-local application which may have caused other dependent services or the tests themselves to not complete within the allocated time.

---

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

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Timeout

The appstudio-e2e-tests/redhat-appstudio-e2e step timed out, causing the Prow job to fail, likely due to underlying infrastructure or configuration issues that delayed test execution.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step failed because the test execution exceeded the allowed timeout of 2 hours. The Prow job was terminated gracefully after the grace period.

Contributing Factors

Several factors in the additional_context suggest potential underlying issues:

• Multiple Argo CD ApplicationSets (application-api, cert-manager, etc.) are in an 'OutOfSync' state, indicating deployment or configuration discrepancies.
• Several resource gathering artifacts failed to parse, suggesting issues with cluster state collection.
• tektonaddons.json and tektonconfigs.json indicate that Tekton Addons and configurations are not fully ready or are experiencing reconciliation issues.
• The must-gather-network-appstudio artifact reports various errors during data gathering, including missing namespaces, secrets, and failures related to Kubernetes resources, indicating potential cluster instability or misconfiguration.
  These environmental problems could be indirectly causing the end-to-end tests to run longer than expected, leading to the timeout.

Impact

The timeout of the primary test execution step prevented the completion of the Prow job, thus blocking the continuous integration pipeline for AppStudio e2e tests.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The end-to-end tests exceeded the allocated timeout of 2 hours, leading to the process being terminated. This suggests that the tests are either too slow, encountering infinite loops, or waiting indefinitely for a condition that is not met.

Logs:

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

{"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-05T16:25:13Z"}

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

{"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-05T16:25:28Z"}

---

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

[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	ada13f8	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.