integration-service update by rh-tap-build-team[bot] · Pull Request #9950 · redhat-appstudio/infra-deployments

rh-tap-build-team · 2026-01-13T10:18:41Z

Included PRs:

github-actions · 2026-01-13T10:18:51Z

🤖 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

Simply type one of the commands above in a comment on this PR
I'll analyze your code and provide detailed feedback
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 · 2026-01-13T10:18:52Z

🤖 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 · 2026-01-13T12:24:30Z

🤖 Pipeline Failure Analysis

Category: Timeout

Pipeline failed due to a timeout during the execution of end-to-end tests.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e job step timed out because the tests exceeded the 2-hour execution limit. The logs indicate that the process did not finish within this timeframe and was subsequently terminated after a grace period.

Contributing Factors

While no specific test failures were reported, the prolonged execution time suggests potential issues such as inefficient test code, excessive resource consumption by the tests, underlying infrastructure slowness, or a transient condition within the test environment that caused delays.

Impact

The timeout prevented the completion of the end-to-end test suite, which is a critical quality gate for validating the functionality of the AppStudio infrastructure. This blocked the progress of the Prow job and did not provide a definitive pass/fail status for the tested components.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The e2e tests exceeded the maximum allowed execution time of 2 hours, leading to a timeout failure. This could be due to slow test execution, resource contention, or an infinite loop within the tests.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/artifacts/e2e-tests.log:1138

{"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-01-13T12:23:50Z"}

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/artifacts/e2e-tests.log:1141

{"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-01-13T12:24:05Z"}

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

konflux-ci-qe-bot · 2026-01-13T16:40:32Z

🤖 Pipeline Failure Analysis

Category: Timeout

The App Studio end-to-end tests failed due to exceeding the allocated 2-hour timeout.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e job exceeded its configured 2-hour timeout. The Prow entrypoint process reported that the main process did not finish before the timeout and subsequently did not exit within the grace period.

Contributing Factors

There are no specific test failures reported, indicating that the issue is likely related to the overall execution time of the test suite, potentially due to environmental slowness, test suite inefficiencies, or an infinite loop/deadlock within the test execution framework itself.

Impact

The timeout prevented the completion of the end-to-end test suite, blocking the successful validation of the App Studio infrastructure deployment for the pull request.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The end-to-end tests exceeded their allocated timeout of 2 hours, indicating that the tests either took too long to complete or got stuck in an infinite loop or a deadlock.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 2396

{"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-01-13T16:39:40Z"}

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 2397

{"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-01-13T16:39:55Z"}

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

konflux-ci-qe-bot · 2026-01-14T11:01:21Z

🤖 Pipeline Failure Analysis

Category: Timeout

Pipeline failed due to a timeout in E2E tests caused by degraded Argo CD application synchronization.

📋 Technical Details

Immediate Cause

The end-to-end tests timed out because critical Argo CD applications, including build-service-in-cluster-local, mintmaker-in-cluster-local, and multi-platform-controller-in-cluster-local, were in a Degraded or Missing state. This prevented the required application synchronization necessary for the tests to begin execution.

Contributing Factors

The underlying cause of the Argo CD application degradation is not immediately apparent from the provided logs. However, the additional_context indicates that the Argo CD instance itself is running and the cluster operators are healthy. The issue appears to be specific to the state of certain deployed applications.

Impact

The failure of these Argo CD applications to synchronize prevented the appstudio-e2e-tests/redhat-appstudio-e2e step from completing within the allocated timeout. This blocked the successful execution of the E2E test suite for this Prow job.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The end-to-end tests failed due to a timeout because several critical Argo CD applications were in a degraded or missing state, preventing timely synchronization and completion of the test setup.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 1201

build-service-in-cluster-local                      Synced      Degraded

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 1202

integration-in-cluster-local                        Synced      Progressing

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 1203

mintmaker-in-cluster-local                          Synced      Degraded

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 1204

multi-platform-controller-in-cluster-local          OutOfSync   Missing

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 1205

pipeline-service-in-cluster-local                   Synced      Progressing

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 1206

release-in-cluster-local                            Synced      Degraded

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 1207

Waiting 10 seconds for application sync

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 2401

{"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-01-14T10:33:00Z"}

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt line 2403

{"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-01-14T10:33:15Z"}

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

openshift-ci · 2026-01-15T11:48:13Z

[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

konflux-ci-qe-bot · 2026-01-15T11:54:51Z

🤖 Pipeline Failure Analysis

Category: Infrastructure

Pipeline failed due to infrastructure issues causing DNS resolution failures and subsequent termination of E2E tests.

📋 Technical Details

Immediate Cause

The primary blocking failure was the inability of the E2E test execution step (appstudio-e2e-tests/redhat-appstudio-e2e) to run successfully, indicated by a "Terminated" signal. This was preceded and likely caused by widespread infrastructure failures related to DNS resolution, preventing various diagnostic and test execution tools from connecting to the cluster's API server.

Contributing Factors

Multiple diagnostic steps (gather-audit-logs, gather-extra, gather-must-gather, redhat-appstudio-gather) failed with identical "no such host" errors when attempting to resolve the cluster API endpoint (api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com). This points to a systemic DNS resolution problem within the test environment or its network configuration, preventing essential tools from interacting with the cluster.

Impact

The DNS resolution failures prevented the collection of crucial diagnostic information and the successful execution of the E2E tests. The main test execution step was terminated, and subsequent diagnostic gathering steps also failed due to the same connectivity issues, leaving limited data to pinpoint the exact root cause of the initial termination.

🔍 Evidence

appstudio-e2e-tests/gather-audit-logs

Category: infrastructure
Root Cause: The failure is caused by a DNS resolution error, preventing the must-gather tool from connecting to the cluster's API server. This is likely due to an issue with the cluster's internal DNS service or network configuration.

Logs:

artifacts/appstudio-e2e-tests/gather-audit-logs/build-log.txt line 5

[must-gather      ] OUT 2026-01-15T11:53:18.463130398Z Get "https://api.konflux-4-17-us-west-2-gv669.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-gv669.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host

artifacts/appstudio-e2e-tests/gather-audit-logs/build-log.txt line 20

error getting cluster version: Get "https://api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com:6443/apis/config.openshift.io/v1/clusterversions/version": dial tcp: lookup api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host

artifacts/appstudio-e2e-tests/gather-audit-logs/build-log.txt line 26

error getting cluster operators: Get "https://api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com:6443/apis/config.openshift.io/v1/clusteroperators": dial tcp: lookup api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host

artifacts/appstudio-e2e-tests/gather-audit-logs/build-log.txt line 34

Error running must-gather collection:
    creating temp namespace: Post "https://api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com:6443/api/v1/namespaces": dial tcp: lookup api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host

artifacts/appstudio-e2e-tests/gather-audit-logs/build-log.txt line 68

error running backup collection: Get "https://api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com:6443/api?timeout=32s": dial tcp: lookup api.konflux-4-17-us-west-2-gv669.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 network connectivity issue, specifically a DNS resolution failure. The job was unable to resolve the hostname of the Kubernetes API server, preventing it from gathering necessary artifacts.

Logs:

artifacts/appstudio-e2e-tests/gather-extra/gather-extra.log line 3

E0115 11:53:10.370367      28 memcache.go:265] couldn't get current server API group list: Get "https://api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com:6443/api?timeout=5s": dial tcp: lookup api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host

artifacts/appstudio-e2e-tests/gather-extra/gather-extra.log line 9

Unable to connect to the server: dial tcp: lookup api.konflux-4-17-us-west-2-gv669.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 command failed due to an inability to connect to the OpenShift API server, indicated by "connection refused" and "no such host" errors. This points to a problem with cluster accessibility or network configuration.

Logs:

artifacts/appstudio-e2e-tests/gather-must-gather/run.log line 17

Error running must-gather collection:
    creating temp namespace: Post "https://api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com:6443/api/v1/namespaces": dial tcp [REDACTED: Public IP (ipv4)]: connection refused

artifacts/appstudio-e2e-tests/gather-must-gather/run.log line 27

E0115 11:53:03.458891      49 memcache.go:265] couldn't get current server API group list: Get "https://api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com:6443/api?timeout=32s": dial tcp: lookup api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host

artifacts/appstudio-e2e-tests/gather-must-gather/run.log line 34

error: creating temp namespace: Post "https://api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com:6443/api/v1/namespaces": dial tcp [REDACTED: Public IP (ipv4)]: connection refused

appstudio-e2e-tests/redhat-appstudio-e2e

Category: infrastructure
Root Cause: The E2E test process was terminated unexpectedly, likely due to an external signal or resource issue, leading to a cascading failure where the process cleanup also failed.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build.log line 656

make: *** [Makefile:25: ci/test/e2e] Terminated

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build.log line 657

{"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-01-15T11:48:06Z"}

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build.log line 659

{"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-01-15T11:48:21Z"}

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build.log line 661

{"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-01-15T11:48:21Z"}

appstudio-e2e-tests/redhat-appstudio-gather

Category: infrastructure
Root Cause: The failure is caused by a DNS resolution issue preventing the oc client from connecting to the Kubernetes API server. The specific error "no such host" indicates that the hostname for the API server could not be resolved to an IP address.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-gather/run.log

E0115 11:53:25.495375      44 memcache.go:265] couldn't get current server API group list: Get "https://api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com:6443/api?timeout=5s": dial tcp: lookup api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host

artifacts/appstudio-e2e-tests/redhat-appstudio-gather/run.log

Unable to connect to the server: dial tcp: lookup api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host

artifacts/appstudio-e2e-tests/redhat-appstudio-gather/run.log

error running backup collection: Get "https://api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com:6443/api?timeout=32s": dial tcp: lookup api.konflux-4-17-us-west-2-gv669.konflux-qe.devcluster.openshift.com on 172.30.0.10:53: no such host

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

openshift-ci Bot requested review from dirgim and jencull January 13, 2026 10:18

rh-tap-build-team Bot force-pushed the integration-service branch from fc0518a to 78cc497 Compare January 13, 2026 14:25

rh-tap-build-team Bot force-pushed the integration-service branch from 80b6a8b to 75c191f Compare January 14, 2026 08:20

rh-tap-build-team Bot force-pushed the integration-service branch 2 times, most recently from 4e5ca3a to ad18983 Compare January 15, 2026 11:08

rh-tap-build-team Bot closed this Jan 15, 2026

rh-tap-build-team Bot force-pushed the integration-service branch from 752e91c to ad18983 Compare January 15, 2026 11:48

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

integration-service update#9950

integration-service update#9950
rh-tap-build-team[bot] wants to merge 0 commit into
mainfrom
integration-service

rh-tap-build-team Bot commented Jan 13, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jan 13, 2026

Uh oh!

github-actions Bot commented Jan 13, 2026

Uh oh!

konflux-ci-qe-bot commented Jan 13, 2026

appstudio-e2e-tests/redhat-appstudio-e2e

Uh oh!

konflux-ci-qe-bot commented Jan 13, 2026

appstudio-e2e-tests/redhat-appstudio-e2e

Uh oh!

konflux-ci-qe-bot commented Jan 14, 2026

appstudio-e2e-tests/redhat-appstudio-e2e

Uh oh!

openshift-ci Bot commented Jan 15, 2026

Uh oh!

konflux-ci-qe-bot commented Jan 15, 2026

appstudio-e2e-tests/gather-audit-logs

appstudio-e2e-tests/gather-extra

appstudio-e2e-tests/gather-must-gather

appstudio-e2e-tests/redhat-appstudio-e2e

appstudio-e2e-tests/redhat-appstudio-gather

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

rh-tap-build-team Bot commented Jan 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Jan 13, 2026

🤖 Gemini AI Assistant Available

Available Commands

How to Use

Permissions

Uh oh!

github-actions Bot commented Jan 13, 2026

Uh oh!

konflux-ci-qe-bot commented Jan 13, 2026

🤖 Pipeline Failure Analysis

📋 Technical Details

Immediate Cause

Contributing Factors

Impact

appstudio-e2e-tests/redhat-appstudio-e2e

Uh oh!

konflux-ci-qe-bot commented Jan 13, 2026

🤖 Pipeline Failure Analysis

📋 Technical Details

Immediate Cause

Contributing Factors

Impact

appstudio-e2e-tests/redhat-appstudio-e2e

Uh oh!

konflux-ci-qe-bot commented Jan 14, 2026

🤖 Pipeline Failure Analysis

📋 Technical Details

Immediate Cause

Contributing Factors

Impact

appstudio-e2e-tests/redhat-appstudio-e2e

Uh oh!

openshift-ci Bot commented Jan 15, 2026

Uh oh!

konflux-ci-qe-bot commented Jan 15, 2026

🤖 Pipeline Failure Analysis

📋 Technical Details

Immediate Cause

Contributing Factors

Impact

appstudio-e2e-tests/gather-audit-logs

appstudio-e2e-tests/gather-extra

appstudio-e2e-tests/gather-must-gather

appstudio-e2e-tests/redhat-appstudio-e2e

appstudio-e2e-tests/redhat-appstudio-gather

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

rh-tap-build-team Bot commented Jan 13, 2026 •

edited

Loading