Skip to content

Conversation

@openshift-ci
Copy link

openshift-ci bot commented Feb 3, 2026

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

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

@github-actions
Copy link
Contributor

github-actions bot commented Feb 3, 2026

🤖 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
Copy link
Contributor

github-actions bot commented Feb 3, 2026

🤖 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
Copy link

🤖 Pipeline Failure Analysis

Category: Timeout

The end-to-end tests timed out due to a failure in synchronizing cluster resources and components, specifically Argo CD ApplicationSets and Tekton components being in an out-of-sync or error state.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step timed out because the underlying test execution was blocked indefinitely while waiting for cluster resources and applications to become ready.

Contributing Factors

Multiple Argo CD ApplicationSets were found in an 'OutOfSync' or 'Unknown' state, indicating that the desired cluster state was not being achieved. Additionally, Tekton resources, specifically tektonaddons.json and tektonconfigs.json, reported errors and non-ready components, including the tkn-cli-serve deployment and general component reconciliation issues. These factors collectively point to an unstable or improperly configured test environment that prevented the e2e tests from proceeding.

Impact

The inability of the cluster environment to reach a stable and synchronized state directly blocked the execution of the end-to-end tests. This prevented any downstream validation or verification steps from running, leading to the overall failure of the Prow job.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The e2e tests timed out because they were stuck waiting for applications and resources to synchronize and become ready in the cluster. This indicates a potential issue with the test environment's readiness or the test setup itself.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt:1068
{"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:28:26Z"}
artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt:1073
{"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:28:41Z"}
artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt:977
build-service-in-cluster-local                      Synced   Degraded

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

@rh-tap-build-team rh-tap-build-team bot force-pushed the caching branch 3 times, most recently from de79dc9 to 63502a7 Compare February 3, 2026 13:20
@konflux-ci-qe-bot
Copy link

🤖 Pipeline Failure Analysis

Category: Infrastructure

The Prow job failed due to a DNS resolution error preventing diagnostic tools from connecting to the OpenShift API, which subsequently led to the termination of the end-to-end tests.

📋 Technical Details

Immediate Cause

Multiple diagnostic and gather steps (appstudio-e2e-tests/gather-audit-logs, appstudio-e2e-tests/gather-extra, appstudio-e2e-tests/gather-must-gather, and appstudio-e2e-tests/redhat-appstudio-gather) failed because they could not resolve the hostname api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com using the DNS server 172.30.0.10:53.

Contributing Factors

The failure of these diagnostic steps directly impacted the appstudio-e2e-tests/redhat-appstudio-e2e step, which was terminated. While the exact reason for the termination of the e2e tests themselves is not explicitly detailed in the provided logs (only that it was "terminated"), the preceding infrastructure failures, particularly the inability to gather necessary cluster state, likely contributed to an unstable testing environment or premature termination by the orchestrator.

Impact

The inability to resolve the OpenShift API server's hostname prevented the successful execution of essential diagnostic data collection steps. This lack of diagnostic information and the underlying network issue caused subsequent test execution to fail or be terminated, preventing the Prow job from completing successfully and verifying the infrastructure deployment.

🔍 Evidence

appstudio-e2e-tests/gather-audit-logs

Category: infrastructure
Root Cause: The must-gather tool failed to connect to the OpenShift API endpoint due to a DNS resolution failure. The tool could not resolve the hostname api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com using the provided DNS server 172.30.0.10:53.

Logs:

artifacts/appstudio-e2e-tests/gather-audit-logs/log.txt line 4
[must-gather      ] OUT 2026-02-03T13:38:54.738253007Z Get "https://api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com:6443/apis/image.openshift.io/v1/namespaces/openshift/imagestreams/must-gather": dial tcp: lookup api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-audit-logs/log.txt line 26
error getting cluster version: Get "https://api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com:6443/apis/config.openshift.io/v1/clusterversions/version": dial tcp: lookup api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-audit-logs/log.txt line 33
error getting cluster operators: Get "https://api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com:6443/apis/config.openshift.io/v1/clusteroperators": dial tcp: lookup api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-audit-logs/log.txt line 42
Error running must-gather collection:
    creating temp namespace: Post "https://api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com:6443/api/v1/namespaces": dial tcp: lookup api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-audit-logs/log.txt line 56
error running backup collection: Get "https://api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com:6443/api?timeout=32s": dial tcp: lookup api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-audit-logs/log.txt line 71
error getting cluster version: Get "https://api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com:6443/apis/config.openshift.io/v1/clusterversions/version": dial tcp: lookup api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-audit-logs/log.txt line 78
error getting cluster operators: Get "https://api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com:6443/apis/config.openshift.io/v1/clusteroperators": dial tcp: lookup api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-audit-logs/log.txt line 85
error: creating temp namespace: Post "https://api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com:6443/api/v1/namespaces": dial tcp: lookup api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host

appstudio-e2e-tests/gather-extra

Category: infrastructure
Root Cause: The gather-extra step failed due to a DNS resolution error when trying to connect to the Kubernetes API server. The cluster's hostname could not be resolved to an IP address.

Logs:

appstudio-e2e-tests/gather-extra
E0203 13:36:17.544826      29 memcache.go:265] couldn't get current server API group list: Get "https://api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com:6443/api?timeout=5s": dial tcp: lookup api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
Unable to connect to the server: dial tcp: lookup api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host

appstudio-e2e-tests/gather-must-gather

Category: infrastructure
Root Cause: The gather-must-gather tool encountered network connectivity issues, specifically "i/o timeout" and "no such host" errors, when attempting to communicate with the OpenShift API server. This prevented the collection of cluster diagnostic data.

Logs:

artifacts/appstudio-e2e-tests/gather-must-gather/log.txt line 17
Error running must-gather collection:
    creating temp namespace: Post "https://api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com:6443/api/v1/namespaces": dial tcp [REDACTED: Public IP (ipv4)]: i/o timeout
artifacts/appstudio-e2e-tests/gather-must-gather/log.txt line 25
E0203 13:25:34.210265      55 memcache.go:265] couldn't get current server API group list: Get "https://api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com:6443/api?timeout=32s": dial tcp: lookup api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-must-gather/log.txt line 49
error: creating temp namespace: Post "https://api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com:6443/api/v1/namespaces": dial tcp [REDACTED: Public IP (ipv4)]: i/o timeout

appstudio-e2e-tests/redhat-appstudio-e2e

Category: infrastructure
Root Cause: The mage process, executing the end-to-end tests, was terminated due to an external interrupt or resource exhaustion, as indicated by the Prow entrypoint logs reporting a "terminated" signal and an inability to kill the process after a grace period.

appstudio-e2e-tests/redhat-appstudio-gather

Category: infrastructure
Root Cause: The oc command failed to connect to the Kubernetes API server due to a DNS lookup failure. This indicates a potential networking or DNS configuration issue within the environment where the command is being executed, preventing it from resolving the API server's hostname.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-gather/logs/appstudio-e2e-tests-516.log
E0203 13:39:02.817219      35 memcache.go:265] couldn't get current server API group list: Get "https://api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com:6443/api?timeout=5s": dial tcp: lookup api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/redhat-appstudio-gather/logs/appstudio-e2e-tests-516.log
Unable to connect to the server: dial tcp: lookup api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/redhat-appstudio-gather/logs/appstudio-e2e-tests-516.log
Error running running must-gather collection:    creating temp namespace: Post "https://api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com:6443/api/v1/namespaces": dial tcp: lookup api.konflux-4-17-us-west-2-ztz85.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host

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

@konflux-ci-qe-bot
Copy link

🤖 Pipeline Failure Analysis

Category: Timeout

Pipeline failed due to a timeout caused by the degraded state of the 'build-service-in-cluster-local' component, stemming from widespread Argo CD synchronization issues across multiple ApplicationSets.

📋 Technical Details

Immediate Cause

The e2e tests timed out because the critical component build-service-in-cluster-local entered a Degraded state and failed to become ready within the allocated time.

Contributing Factors

The build-service-in-cluster-local component's degraded state is attributed to broader cluster synchronization problems. Analysis of additional_context shows that the build-service-in-cluster-local Argo CD Application is Degraded, and its build-service-controller-manager Deployment has exceeded its progress deadline. Concurrently, numerous ApplicationSet resources, including application-api, are in an OutOfSync state, indicating a systemic issue with Argo CD's ability to reconcile desired states across the cluster. Additionally, Tekton Addon components are reported as not ready, citing issues with OpenShift console resources and the tkn-cli-serve deployment, which may be indirectly related to the application synchronization failures.

Impact

The failure of the build-service-in-cluster-local component to become ready prevented the execution of the appstudio e2e tests, causing the job to time out. This blocked the validation of the deployed infrastructure components and prevented the successful completion of the CI pipeline.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The e2e tests timed out because a critical component, 'build-service-in-cluster-local', entered a degraded state and failed to become ready, preventing the tests from completing within the allocated time.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/job.log:1473
build-service-in-cluster-local                      Synced   Degraded
artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/job.log:1477
Waiting 10 seconds for application sync
artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/job.log:1492
{"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-03T15:24:08Z"}
artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/job.log:1497
{"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-03T15:24:23Z"}

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant