Skip to content

caching.git update #10337

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
rh-tap-build-team wants to merge 0 commits into from
Closed

caching.git update #10337

rh-tap-build-team wants to merge 0 commits into from
+0 −0

Conversation

@rh-tap-build-team
Copy link
Contributor

@rh-tap-build-team rh-tap-build-team bot commented Feb 2, 2026 •
edited
Loading

@openshift-ci openshift-ci bot requested review from amisstea and avi-biton February 2, 2026 11:45
@github-actions
Copy link
Contributor

github-actions bot commented Feb 2, 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 2, 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.

@rh-tap-build-team rh-tap-build-team bot force-pushed the caching.git branch 2 times, most recently from 475b57a to 702b730 Compare February 2, 2026 14:04
@konflux-ci-qe-bot
Copy link

konflux-ci-qe-bot commented Feb 2, 2026

🤖 Pipeline Failure Analysis

Category: Infrastructure

The Prow job failed due to a DNS resolution error preventing access to the OpenShift API server, which subsequently caused artifact collection steps to fail and the main e2e tests to time out.

📋 Technical Details

Immediate Cause

The Prow job failed because multiple steps (gather-audit-logs, gather-extra, redhat-appstudio-gather) were unable to resolve the hostname api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com. This DNS lookup failure, evidenced by repeated "no such host" errors in the logs, prevented these steps from successfully connecting to the OpenShift API server and gathering necessary artifacts.

Contributing Factors

The inability to connect to the API server likely contributed to the redhat-appstudio-e2e tests timing out. Without the ability to collect diagnostic data or properly interact with the cluster, the tests could not proceed and eventually exceeded their allocated runtime. The provided must-gather log also explicitly mentions similar DNS resolution issues, reinforcing the infrastructure-level nature of the problem.

Impact

This infrastructure failure critically blocked the pipeline by preventing the successful collection of diagnostic logs and artifacts. Consequently, the main e2e test execution was impacted, leading to a timeout and an inability to validate the deployed application or its environment.

🔍 Evidence

appstudio-e2e-tests/gather-audit-logs

Category: infrastructure
Root Cause: The must-gather tool failed to resolve the hostname of the OpenShift API server due to a DNS lookup failure, indicating a networking or DNS configuration problem within the environment.

Logs:

artifacts/appstudio-e2e-tests/gather-audit-logs/steps.log line 3 
[must-gather      ] OUT 2026-02-02T14:03:51.045537804Z Get "https://api.konflux-4-17-us-west-2-g6fdp.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-g6fdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-audit-logs/steps.log line 15 
error getting cluster version: Get "https://api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com:6443/apis/config.openshift.io/v1/clusterversions/version": dial tcp: lookup api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-audit-logs/steps.log line 20 
error getting cluster operators: Get "https://api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com:6443/apis/config.openshift.io/v1/clusteroperators": dial tcp: lookup api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-audit-logs/steps.log line 25 
Error running must-gather collection:
    creating temp namespace: Post "https://api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com:6443/api/v1/namespaces": dial tcp: lookup api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-audit-logs/steps.log line 45 
error running backup collection: Get "https://api.konflux-4-17-us-west-2-g6fdp.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com:6443/api?timeout=32s": dial tcp: lookup api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-audit-logs/steps.log line 67 
error: creating temp namespace: Post "https://api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com:6443/api/v1/namespaces": dial tcp: lookup api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host

appstudio-e2e-tests/gather-extra

Category: infrastructure
Root Cause: The CI job failed to gather artifacts because it could not resolve the DNS of the Kubernetes API server (api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com), indicating a network or DNS configuration issue within the cluster or the job's environment.

Logs:

artifacts/appstudio-e2e-tests/gather-extra/log.txt line 307 
dial tcp: lookup api.konflux-4-17-us-west-2gfdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-extra/log.txt line 146 
dial tcp: lookup api.konflux-4-17-us-west-2gfdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-extra/log.txt line 516 
dial tcp: lookup api.konflux-4-17-us-west-2gfdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-extra/log.txt line 976 
dial tcp: lookup api.konflux-4-17-us-west-2gfdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-extra/log.txt line 1598 
dial tcp: lookup api.konflux-4-17-us-west-2gfdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-extra/log.txt line 2230 
dial tcp: lookup api.konflux-4-17-us-west-2gfdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-extra/log.txt line 2858 
dial tcp: lookup api.konflux-4-17-us-west-2gfdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-extra/log.txt line 3612 
dial tcp: lookup api.konflux-4-17-us-west-2gfdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-extra/log.txt line 4108 
dial tcp: lookup api.konflux-4-17-us-west-2gfdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The e2e tests timed out, indicating that the test execution took longer than the allowed time limit of 2 hours. This could be due to slow test execution, resource contention, or an issue with the test environment itself.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 1584 
{"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-02T13:50:58Z"}
artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 1586 
{"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-02T13:51:13Z"}

appstudio-e2e-tests/redhat-appstudio-gather

Category: infrastructure
Root Cause: The primary cause of the failure is an inability to resolve the hostname of the OpenShift API server. This suggests a networking or DNS configuration issue preventing the oc client from connecting to the cluster.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-gather/log.txt line 22 
E0202 14:06:10.861992      91 memcache.go:265] couldn't get current server API group list: Get "https://api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com:6443/api?timeout=5s": dial tcp: lookup api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/redhat-appstudio-gather/log.txt line 459 
Unable to connect to the server: dial tcp: lookup api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/redhat-appstudio-gather/log.txt line 461 
Error running must-gather collection:
    creating temp namespace: Post "https://api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com:6443/api/v1/namespaces": dial tcp: lookup api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/redhat-appstudio-gather/log.txt line 474 
error running backup collection: Get "https://api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com:6443/api?timeout=32s": dial tcp: lookup api.konflux-4-17-us-west-2-g6fdp.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host

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

@rh-tap-build-team rh-tap-build-team bot force-pushed the caching.git branch 2 times, most recently from 0a1f229 to 3461821 Compare February 2, 2026 16:12
@konflux-ci-qe-bot
Copy link

konflux-ci-qe-bot commented Feb 2, 2026

🤖 Pipeline Failure Analysis

Category: Infrastructure

The Prow job failed due to infrastructure issues preventing network connectivity to the OpenShift API server, which led to subsequent timeouts and data gathering failures.

📋 Technical Details

Immediate Cause

The Prow job's gather steps (e.g., appstudio-e2e-tests/gather-audit-logs, appstudio-e2e-tests/gather-extra, appstudio-e2e-tests/gather-must-gather, appstudio-e2e-tests/redhat-appstudio-gather) failed because they could not connect to the OpenShift API server. This was due to DNS resolution failures ("no such host") and network timeouts ("i/o timeout") when attempting to reach api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com.

Contributing Factors

The failure to collect audit logs and other diagnostic information in the initial gather steps likely contributed to the main test execution step (appstudio-e2e-tests/redhat-appstudio-e2e) eventually timing out. The inability to communicate with the cluster's API server meant that essential Prow job components and the tests themselves could not operate correctly.

Impact

The network connectivity and DNS resolution issues prevented the Prow job from collecting critical diagnostic artifacts and performing its intended end-to-end tests. This ultimately led to the job being terminated due to timeout, preventing successful validation of the pull request.

🔍 Evidence

appstudio-e2e-tests/gather-audit-logs

Category: infrastructure
Root Cause: The must-gather tool failed to connect to the OpenShift API server due to a DNS lookup failure or network connectivity issue. This prevented it from collecting audit logs and other cluster information.

Logs:

artifacts/appstudio-e2e-tests/gather-audit-logs/gather-audit-logs.log line 4 
[must-gather      ] OUT 2026-02-02T16:13:23.322385577Z Get "https://api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com:6443/apis/image.openshift.io/v1/namespaces/openshift/imagestreams/must-gather": dial tcp [REDACTED: Public IP (ipv4)]: i/o timeout
artifacts/appstudio-e2e-tests/gather-audit-logs/gather-audit-logs.log line 17 
error getting cluster version: Get "https://api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com:6443/apis/config.openshift.io/v1/clusterversions/version": dial tcp: lookup api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-audit-logs/gather-audit-logs.log line 22 
error getting cluster operators: Get "https://api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com:6443/apis/config.openshift.io/v1/clusteroperators": dial tcp: lookup api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-audit-logs/gather-audit-logs.log line 27 
Error running must-gather collection:
    creating temp namespace: Post "https://api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com:6443/api/v1/namespaces": dial tcp: lookup api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-audit-logs/gather-audit-logs.log line 48 
error running backup collection: Get "https://api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com:6443/api?timeout=32s": dial tcp: lookup api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host

appstudio-e2e-tests/gather-extra

Category: infrastructure
Root Cause: The step failed due to a network connectivity issue, specifically an inability to resolve the DNS name of the Kubernetes API server, which is required for gathering artifacts.

Logs:

artifacts/appstudio-e2e-tests/gather-extra/gather-extra.log line 3 
E0202 16:12:40.832581      26 memcache.go:265] couldn't get current server API group list: Get "https://api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com:6443/api?timeout=5s": dial tcp: lookup api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-extra/gather-extra.log line 15 
Unable to connect to the server: dial tcp: lookup api.konflux-4-17-us-west-2-gjv8c.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 oc adm must-gather command failed due to network connectivity issues, specifically "i/o timeout" and "no such host" errors when attempting to reach the OpenShift API server. This suggests a problem with the network infrastructure or DNS resolution for the cluster.

Logs:

artifacts/appstudio-e2e-tests/gather-must-gather/logs/step.log:13 
Error running must-gather collection:
    creating temp namespace: Post "https://api.konflux-4-17-us-west-2-gjv8c.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/logs/step.log:21 
E0202 16:12:26.067388      47 memcache.go:265] couldn't get current server API group list: Get "https://api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com:6443/api?timeout=32s": dial tcp [REDACTED: Public IP (ipv4)]: i/o timeout
artifacts/appstudio-e2e-tests/gather-must-gather/logs/step.log:22 
E0202 16:12:26.080009      47 memcache.go:265] couldn't get current server API group list: Get "https://api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com:6443/api?timeout=32s": dial tcp: lookup api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-must-gather/logs/step.log:33 
error running backup collection: Get "https://api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com:6443/api?timeout=32s": dial tcp: lookup api.konflux-4-17-us-west-2-gjv8c.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/gather-must-gather/logs/step.log:34 
error: creating temp namespace: Post "https://api.konflux-4-17-us-west-2-gjv8c.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: timeout
Root Cause: The job terminated due to exceeding its allocated time limit. The entrypoint process was interrupted, and after a grace period, the system attempted to forcefully terminate it, indicating a timeout event.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 1339 
I0202 16:07:18Z {"component":"entrypoint","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:173","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2026-02-02T16:07:18Z"}
artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 1340 
make: *** [Makefile:25: ci/test/e2e] Terminated
artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 1344 
I0202 16:07:33Z {"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-02T16:07:33Z"}
artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 1345 
{"component":"entrypoint","error":"os: process already finished","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:269","func":"sigs.k8s.io/prow/pkg/entrypoint.gracefullyTerminate","level":"error","msg":"Could not kill process after grace period","severity":"error","time":"2026-02-02T16:07:33Z"}

appstudio-e2e-tests/redhat-appstudio-gather

Category: infrastructure
Root Cause: The oc client is unable to resolve the hostname of the Kubernetes API server, indicating a DNS resolution issue or network connectivity problem preventing access to the cluster.

Logs:

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

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

@konflux-ci-qe-bot
Copy link

konflux-ci-qe-bot commented Feb 2, 2026

🤖 Pipeline Failure Analysis

Category: Timeout

The Red Hat AppStudio E2E tests timed out, indicating a prolonged execution that exceeded the allocated 2-hour limit.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step failed because it exceeded the 2-hour timeout limit. The Prow entrypoint explicitly logged that the process did not finish within the allowed duration and subsequently did not exit gracefully within the grace period.

Contributing Factors

While no single test failure or step failure directly preceded the timeout, several environmental factors suggest a potentially unhealthy or out-of-sync cluster state that could have contributed to the extended test execution time. These include:

  • The build-service-in-cluster-local Argo CD Application being in a 'Degraded' state.
  • Numerous ApplicationSets being in an 'OutOfSync' status, with some having selfHeal disabled.
  • The TektonAddon addon being in an error state due to the tkn-cli-serve deployment not being ready, and TektonConfig components not being in a ready state.
  • The static-admission AdmissionCheck being active with a retry delay.

These conditions may have led to delays in resource provisioning, application deployment, or test setup, ultimately causing the end-to-end tests to run longer than anticipated.

Impact

The timeout prevented the completion of the Red Hat AppStudio E2E tests, which are critical for validating the functionality and stability of the AppStudio infrastructure. This failure means that the Pull Request cannot be validated, potentially blocking the integration of changes into the main branch.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The end-to-end tests failed due to exceeding the allocated 2-hour timeout. This indicates that the tests themselves, or a process they rely on, ran for too long.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 700 
{"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-02T18:23:06Z"}
artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 702 
{"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-02T18:23:21Z"}

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

@konflux-ci-qe-bot
Copy link

konflux-ci-qe-bot commented Feb 2, 2026

🤖 Pipeline Failure Analysis

Category: Timeout

The AppStudio E2E tests timed out, preventing the successful completion of the Prow job.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step exceeded its allocated execution time of 2 hours, leading to a timeout. The underlying process also failed to terminate within the subsequent 15-second grace period.

Contributing Factors

While no specific test failures were logged, the broader cluster state indicates potential underlying issues. Several ArgoCD ApplicationSets, including build-service, are reported as OutOfSync. Additionally, the tektonaddons.json and tektonconfigs.json artifacts show that some Tekton components, such as tkn-cli-serve, are not ready. These issues could contribute to a degraded performance or an unstable environment, potentially leading to the test suite taking an unusually long time to execute or getting stuck.

Impact

The timeout directly blocked the completion of the Prow job, failing the CI pipeline and preventing the validation of infrastructure deployments for AppStudio.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The e2e tests timed out, likely due to a long-running or stuck test process that exceeded the allocated execution time.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step_log.txt line 695 
{"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-02T23:11:19Z"}
artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step_log.txt line 698 
{"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-02T23:11:34Z"}

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

@rh-tap-build-team rh-tap-build-team bot force-pushed the caching.git branch 2 times, most recently from 859a958 to 4a70991 Compare February 3, 2026 07:19
@konflux-ci-qe-bot
Copy link

konflux-ci-qe-bot commented Feb 3, 2026

🤖 Pipeline Failure Analysis

Category: Timeout

The e2e tests timed out due to an inability to connect to the cluster's API server, likely caused by a DNS resolution failure.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step failed with a timeout. The logs show a specific error message: "Unable to connect to the server: dial tcp: lookup api.konflux-4-17-us-west-2-qjvbq.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host". This indicates a failure in resolving the DNS name of the Kubernetes API server.

Contributing Factors

While the root cause is a DNS resolution failure, the additional_context reveals potential underlying issues within the cluster's networking and Tekton components. Specifically, the tektonaddons.json shows that the tkn-cli-serve deployment is not ready, and tektonconfigs.json indicates that TektonAddon needs to reconcile again, leading to ComponentsReady being False. These could indirectly impact cluster stability and network services necessary for API server accessibility. The must-gather-network-appstudio also shows network-related errors during data collection.

Impact

The inability to reach the cluster's API server prevented the execution of the end-to-end tests. This blocked the validation of the AppStudio infrastructure deployment, preventing any further progress or validation of the changes introduced by the pull request.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The e2e tests timed out because the cluster's API server was unreachable during the test execution, likely due to a DNS resolution failure, preventing the tests from completing within the allocated time.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.log line 434 
Unable to connect to the server: dial tcp: lookup api.konflux-4-17-us-west-2-qjvbq.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host
artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.log line 521 
{"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:33Z"}
artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.log line 524 
{"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:48Z"}

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

@rh-tap-build-team rh-tap-build-team bot force-pushed the caching.git branch 2 times, most recently from 09690b2 to 4a70991 Compare February 3, 2026 10:51
@rh-tap-build-team rh-tap-build-team bot closed this Feb 3, 2026
@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]

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

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

Reviewers

@amisstea amisstea Awaiting requested review from amisstea

@avi-biton avi-biton Awaiting requested review from avi-biton

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@konflux-ci-qe-bot