fix: Fixing kubernetes-cluster-monitoring dashboard

[jhutar]

No description provided.

[github-actions]

🤖 Gemini AI Assistant Available

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

[jhutar]

/retest

[rh-hemartin]

/lgtm

[FaisalAl-Rayes]

LGTM

[hugares]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: FaisalAl-Rayes, hugares, jhutar

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/monitoring/OWNERS [FaisalAl-Rayes,hugares]

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 test job timed out because the test execution exceeded the allowed duration, likely due to underlying infrastructure and application deployment issues within the cluster.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step exceeded the maximum allowed execution time of 2 hours, resulting in a job timeout.

Contributing Factors

Analysis of the cluster state reveals several contributing factors:

• Multiple ArgoCD applications, including build-service-in-cluster-local and pipeline-service-in-cluster-local, are in a 'Degraded' or 'OutOfSync' state.
• Numerous ApplicationSet resources are also in an 'OutOfSync' state, indicating deployment or configuration problems for various application components.
• The tektonaddons and tektonconfigs artifacts indicate that essential Tekton components, specifically 'openshift console resources' and 'tkn-cli-serve deployment', are not ready and are experiencing issues. This suggests that the necessary environments or services for running e2e tests might not have been fully operational.

Impact

The prolonged execution time caused by these underlying issues prevented the e2e tests from completing within the allotted timeframe. This blocked the successful completion of the Prow job and thus the validation of the infrastructure deployments for AppStudio.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The e2e test job timed out because one or more of the setup, configuration, or test execution steps took longer than the maximum allowed duration of 2 hours.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/latest/build.log:307

{"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-02T17:30:50Z"}

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/latest/build.log:309

{"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-02T17:31:05Z"}

---

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

[rh-hemartin]

/lgtm

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Timeout

The Red Hat AppStudio end-to-end tests timed out due to prolonged execution, likely exacerbated by underlying infrastructure issues including degraded deployments and unready Tekton components.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step failed because it exceeded the configured 2-hour timeout limit. The Prow entrypoint process indicated that the process did not finish within the allocated time and subsequently did not exit within the grace period.

Contributing Factors

Analysis of the additional context reveals potential contributing factors to the extended test execution time. Several Argo CD ApplicationSets are in an 'OutOfSync' or 'Progressing' state, and the build-service-controller-manager deployment is in a 'Degraded' state. Furthermore, Tekton Addons are reporting that the tkn-cli-serve deployment is not ready, and the TektonConfig indicates that its components are not ready, specifically mentioning TektonAddon reconciliation issues. These infrastructure and component readiness issues could lead to delays in test setup, execution, or resource provisioning, thereby increasing the overall test run duration.

Impact

The timeout failure prevented the completion of the end-to-end test suite for Red Hat AppStudio. This directly blocked the pipeline from progressing and validating the deployed infrastructure, leaving the status of the changes in PR #10303 unverified by these tests.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The end-to-end tests for Red Hat AppStudio exceeded the allocated 2-hour timeout limit. This indicates that the tests took too long to complete, possibly due to performance issues, test flakiness, or an excessive number of tests.

Logs:

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

{"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-03T09:54:59Z"}

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

{"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-03T09:55:14Z"}

---

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

[openshift-ci]

@jhutar: 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	e4b7bf3	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.