release-service update

[rh-tap-build-team]

Included PRs:

• feat(RELEASE-2027): add renovate link check konflux-ci/release-service#1272
• chore(deps): update opentelemetry-go monorepo to v1.40.0 konflux-ci/release-service#1279

[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: Infrastructure

Pipeline failed due to exceeding Docker registry unauthenticated pull rate limits when deploying the PostgreSQL Helm chart.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step failed because the pipeline encountered "429 Too Many Requests" errors when attempting to pull the PostgreSQL Helm chart from the Docker registry. This indicates that the rate limits for unauthenticated pulls were exceeded, preventing the successful acquisition of the necessary chart.

Contributing Factors

The additional context reveals that multiple Argo CD applications, including the postgres application, show degraded or unknown sync statuses. The failure of the postgres application to sync is explicitly attributed to the "Too Many Requests" error when pulling its Helm chart, directly linking the infrastructure issue to a specific component deployment failure.

Impact

This infrastructure failure prevented the successful deployment of critical components, specifically the PostgreSQL Helm chart, which is a prerequisite for the e2e tests to complete. As a result, the entire appstudio-e2e-tests job was blocked and could not proceed to its validation stages.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: infrastructure
Root Cause: The pipeline failed because it exceeded the unauthenticated pull rate limit for the Docker registry while attempting to pull the PostgreSQL Helm chart. This resulted in repeated "429 Too Many Requests" errors, preventing the successful deployment of necessary components.

---

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

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Timeout

The AppStudio end-to-end tests timed out, preventing the successful completion of the job.

📋 Technical Details

Immediate Cause

The redhat-appstudio-e2e test step exceeded its allocated execution time of 2 hours, resulting in a timeout and job failure.

Contributing Factors

Analysis of the additional_context reveals potential underlying infrastructure or configuration issues that may have contributed to the extended test execution time. Specifically, the tektonaddons.json indicates that the Tekton Addon is not fully ready due to issues with console resource readiness and the TKN CLI serving deployment. Furthermore, tektonconfigs.json shows that Tekton components are not in a ready state, with a message suggesting a reconciliation is needed for the Tekton Addon. These readiness issues within the Tekton ecosystem could be impacting the performance and stability of the end-to-end tests.

Impact

The timeout of the end-to-end tests prevented any further steps from executing and blocked the overall completion of the pull-ci-redhat-appstudio-infra-deployments-main-appstudio-e2e-tests job. This means that the quality and correctness of the AppStudio infrastructure could not be validated by this job run.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The end-to-end tests for the redhat-appstudio-e2e component timed out, indicating that the test suite or its dependencies exceeded the allocated execution time.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step_log.txt:376

{"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-03T04:50:22Z"}

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step_log.txt:378

{"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-03T04:50:37Z"}

---

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

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rh-tap-build-team[bot]

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

Details

Needs approval from an approver in each of these files:

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