integration-service update

[rh-tap-build-team]

Included PRs:

• fix(STONEINTG-1441): remove schedule from renovate config file konflux-ci/integration-service#1444
• fix(STONEINTG-1408): update the gitlab comment logic konflux-ci/integration-service#1443
• chore(deps): update registry.access.redhat.com/ubi9/go-toolset docker tag to v9 konflux-ci/integration-service#1450

[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 infrastructure issues preventing E2E tests from connecting to the cluster API server.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step failed because the main test process was terminated prematurely. This termination is indicated by make: *** [Makefile:25: ci/test/e2e] Terminated and Prow entrypoint logs stating Entrypoint received interrupt: terminated and Process did not exit before 15s grace period. This premature termination was a consequence of the preceding infrastructure failures.

Contributing Factors

Multiple infrastructure-level steps (gather-audit-logs, gather-extra, gather-must-gather, redhat-appstudio-gather) failed due to an inability to resolve the hostname of the OpenShift API server (api.konflux-4-17-us-west-2-kjkrv.konflux-qe.devcluster.openshift.com). Evidence consistently shows dial tcp: lookup ... on 172.30.0.10:53: no such host or i/o timeout, indicating a fundamental network or DNS configuration problem within the test cluster environment. These failures prevented the collection of necessary diagnostic data, likely contributing to the eventual termination of the E2E test process.

Impact

The persistent DNS resolution failures prevented essential diagnostic data collection during the gather-audit-logs, gather-extra, and gather-must-gather steps. This network connectivity issue also directly impacted the redhat-appstudio-gather step. Ultimately, these underlying infrastructure problems led to the premature termination of the main redhat-appstudio-e2e test execution, blocking the successful completion of the E2E test suite.

🔍 Evidence

appstudio-e2e-tests/gather-audit-logs

Category: infrastructure
Root Cause: The must-gather tool is unable to resolve the hostname of the OpenShift API server, likely due to a DNS or network configuration issue within the cluster environment. This prevents it from collecting audit logs and other cluster information.

Logs:

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

[must-gather      ] OUT 2026-02-02T15:54:23.859893464Z Get "https://api.konflux-4-17-us-west-2-kjkrv.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-kjkrv.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 16

error getting cluster version: Get "https://api.konflux-4-17-us-west-2-kjkrv.konflux-qe.devcluster.openshift.com:6443/apis/config.openshift.io/v1/clusterversions/version": dial tcp: lookup api.konflux-4-17-us-west-2-kjkrv.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 operators: Get "https://api.konflux-4-17-us-west-2-kjkrv.konflux-qe.devcluster.openshift.com:6443/apis/config.openshift.io/v1/clusteroperators": dial tcp: lookup api.konflux-4-17-us-west-2-kjkrv.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 31

Error running must-gather collection:
    creating temp namespace: Post "https://api.konflux-4-17-us-west-2-kjkrv.konflux-qe.devcluster.openshift.com:6443/api/v1/namespaces": dial tcp: lookup api.konflux-4-17-us-west-2-kjkrv.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 58

error running backup collection: Get "https://api.konflux-4-17-us-west-2-kjkrv.konflux-qe.devcluster.openshift.com:6443/api?timeout=32s": dial tcp: lookup api.konflux-4-17-us-west-2-kjkrv.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 76

error: creating temp namespace: Post "https://api.konflux-4-17-us-west-2-kjkrv.konflux-qe.devcluster.openshift.com:6443/api/v1/namespaces": dial tcp: lookup api.konflux-4-17-us-west-2-kjkrv.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 because it could not resolve the DNS of the Kubernetes API server, likely due to a network misconfiguration or an issue with the cluster's DNS services.

Logs:

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

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

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

Unable to connect to the server: dial tcp: lookup api.konflux-4-17-us-west-2-kjkrv.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 must-gather tool encountered network issues, specifically I/O timeouts and DNS resolution failures, when attempting to connect to the OpenShift API server, indicating a problem with cluster accessibility or network configuration.

Logs:

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

Error running must-gather collection:
    creating temp namespace: Post "https://api.konflux-4-17-us-west-2-kjkrv.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/build.log line 25

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

artifacts/appstudio-e2e-tests/gather-must-gather/build.log line 37

E0202 15:54:02.192293      54 memcache.go:265] couldn't get current server API group list: Get "https://api.konflux-4-17-us-west-2-kjkrv.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/build.log line 48

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

appstudio-e2e-tests/redhat-appstudio-e2e

Category: unknown
Root Cause: The E2E tests failed because the main process running them was terminated prematurely, likely due to a timeout or an unhandled signal from the environment. This termination prevented the tests from completing successfully.

Logs:

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

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

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

{"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-02T15:49:14Z"}

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

{"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-02T15:49:29Z"}

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

{"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-02T15:49:29Z"}

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

pipeline-service-in-cluster-local                   OutOfSync   Degraded

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 for the cluster's API endpoint. This suggests an issue with network connectivity or DNS resolution for the cluster.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-gather/log.txt line 10

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

artifacts/appstudio-e2e-tests/redhat-appstudio-gather/log.txt line 1731

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

artifacts/appstudio-e2e-tests/redhat-appstudio-gather/log.txt line 4398

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

---

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

[dirgim]

/lgtm
/approve

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Timeout

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

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step in the Prow job exceeded its 2-hour timeout. The process was terminated after failing to exit within the allowed time and a subsequent grace period.

Contributing Factors

Analysis of the additional context reveals potential contributing factors to the prolonged test execution. Multiple ArgoCD Applications are in an 'OutOfSync' or 'Missing' health state, and the 'build-service-controller-manager' Deployment is in a 'Degraded' state. Furthermore, the Tekton Addon component's 'tkn-cli-serve' deployment is experiencing issues, preventing its readiness. These environmental instabilities could have negatively impacted the performance and duration of the E2E tests.

Impact

The timeout of the E2E tests step prevented the Prow job from completing its execution, thus blocking the validation of infrastructure deployments for AppStudio on the main branch.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The e2e tests exceeded the configured timeout of 2 hours, causing the process to be terminated. This could be due to slow test execution, resource contention, or an issue within the test environment itself.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step_log.txt line 1360

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

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step_log.txt line 1363

{"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:55:28Z"}

---

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

[14rcole]

/test appstudio-e2e-tests

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Infrastructure

Pipeline failed due to Docker Hub rate limiting preventing the download of a required PostgreSQL Helm chart.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step failed because the build environment was rate-limited by Docker Hub. Specifically, the job received a "429 Too Many Requests" error when attempting to pull the Helm chart for PostgreSQL from registry-1.docker.io/bitnamichartssecure/postgresql.

Contributing Factors

This rate limiting is an infrastructure issue external to the pipeline's code or configuration. The necessity of pulling this chart for the PostgreSQL deployment, which is a dependency for the e2e tests, directly led to the failure when external resource access was throttled.

Impact

The inability to download the PostgreSQL Helm chart prevented the successful deployment of required services for the end-to-end tests. This blocked the execution of the test suite, causing the Prow job to fail.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: infrastructure
Root Cause: The build environment exceeded the unauthenticated pull rate limit for Docker Hub (registry-1.docker.io), preventing the necessary Helm chart for PostgreSQL from being downloaded. This infrastructure-level rate limiting disrupted the deployment of required services for the e2e tests.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/log.txt line 273

postgres failed with:
[{"lastTransitionTime":"2026-02-02T20:23:24Z","message":"Failed to load target state: failed to generate manifest for source 1 of 1: rpc error: code = Unknown desc = error pulling OCI chart: failed to pull OCI chart: failed to get command args to log: 'helm pull oci://registry-1.docker.io/bitnamichartssecure/postgresql --version 17.0.2 --destination /tmp/a9d99e7c-1300-438f-be8d-60c9fef557eb' failed exit status 1: Error: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/bitnamichartssecure/postgresql/manifests/sha256:6761aad2d5e01b5462284aa31f1c58e676deee8b8266491f95b22ecfd0f1113d: 429 Too Many Requests - Server message: toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit","type":"ComparisonError"}]

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/log.txt line 370

postgres failed with:
[{"lastTransitionTime":"2026-02-02T20:28:16Z","message":"Failed to load target state: failed to generate manifest for source 1 of 1: rpc error: code = Unknown desc = error pulling OCI chart: failed to pull OCI chart: failed to get command args to log: 'helm pull oci://registry-1.docker.io/bitnamichartssecure/postgresql --version 17.0.2 --destination /tmp/908ce2d0-6ed7-4fa9-8844-d2565daf5d8e' failed exit status 1: Error: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/bitnamichartssecure/postgresql/manifests/sha256:6761aad2d5e01b5462284aa31f1c58e676deee8b8266491f95b22ecfd0f1113d: 429 Too Many Requests - Server message: toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit","type":"ComparisonError"}]

---

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

[hongweiliu17]

/test appstudio-e2e-tests

[hongweiliu17]

/approve
/lgtm

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Timeout

The end-to-end test suite timed out, preventing the successful completion of the Prow job.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step timed out after exceeding the allocated 2-hour execution limit. The Prow entrypoint process was terminated due to this timeout.

Contributing Factors

Multiple Argo CD applications, including all-application-sets and application-api, are in an 'OutOfSync' or 'Degraded' state. Additionally, Tekton components are not fully ready, specifically the tkn-cli-serve deployment within the OpenShift console is not ready, as indicated by the tektonaddons.json and tektonconfigs.json artifacts. These environmental issues likely caused delays or prevented necessary test setup/execution, leading to the overall timeout.

Impact

The timeout of the end-to-end tests blocked the successful completion of the Prow job, preventing the validation of the infrastructure deployments. This means any potential regressions or configuration issues in the tested components were not detected.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The end-to-end tests timed out because the processes involved in their execution exceeded the allocated time limit, likely due to issues with test duration or resource contention.

Logs:

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

{"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-03T03:37:46Z"}

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

{"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-03T03:38:01Z"}

---

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

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Infrastructure

Pipeline failed due to infrastructure issues with Docker Hub rate limiting, preventing the installation of PostgreSQL Helm chart and subsequent E2E test execution.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step failed because the job encountered HTTP 429 "Too Many Requests" errors when trying to pull the PostgreSQL Helm chart from registry-1.docker.io/bitnamichartssecure/postgresql. This indicates that the rate limits imposed by Docker Hub were exceeded.

Contributing Factors

While the immediate cause is rate limiting, the underlying reason for frequent pulls or potentially unauthenticated pulls could be related to the CI environment's network configuration or caching mechanisms. The provided additional_context reveals several degraded Argo CD ApplicationSets and a tkn-cli-serve deployment not being ready, which could indirectly contribute to a less stable environment or indicate pre-existing issues that are exacerbated by external dependencies like Docker Hub. However, these are secondary to the direct cause of the job failure.

Impact

This failure completely blocked the execution of the appstudio-e2e-tests/redhat-appstudio-e2e job. Without the successful installation of the PostgreSQL Helm chart, the dependent services could not be provisioned in the test cluster, preventing any E2E tests from running and ultimately halting the pipeline's progress.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: infrastructure
Root Cause: The failure is caused by hitting the rate limit when pulling the PostgreSQL Helm chart from the Docker registry. This prevents the necessary components from being installed in the cluster, leading to the failure of the bootstrapping process.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.log line 684

postgres failed with:
[{"lastTransitionTime":"2026-02-03T04:46:22Z","message":"Failed to load target state: failed to generate manifest for source 1 of 1: rpc error: code = Unknown desc = error pulling OCI chart: failed to pull OCI chart: failed to get command args to log: 'helm pull oci://registry-1.docker.io/bitnamichartssecure/postgresql --version 17.0.2 --destination /tmp/73a383a9-51c7-475f-b5de-c550d9deeff5' failed exit status 1: Error: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/bitnamichartssecure/postgresql/manifests/sha256:6761aad2d5e01b5462284aa31f1c58e676deee8b8266491f95b22ecfd0f1113d: 429 Too Many Requests - Server message: toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit","type":"ComparisonError"}]

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.log line 965

postgres failed with:
[{"lastTransitionTime":"2026-02-03T05:07:23Z","message":"Failed to load target state: failed to generate manifest for source 1 of 1: rpc error: code = Unknown desc = error pulling OCI chart: failed to pull OCI chart: failed to get command args to log: 'helm pull oci://registry-1.docker.io/bitnamichartssecure/postgresql --version 17.0.2 --destination /tmp/a0fb0f75-4b1d-4161-85bf-9d782a94ff46' failed exit status 1: Error: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/bitnamichartssecure/postgresql/manifests/sha256:6761aad2d5e01b5462284aa31f1c58e676deee8b8266491f95b22ecfd0f1113d: 429 Too Many Requests - Server message: toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit","type":"ComparisonError"}]

---

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

[hongweiliu17]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 14rcole, dirgim, hongweiliu17, rh-tap-build-team[bot]

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/integration/OWNERS [14rcole,dirgim,hongweiliu17]

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

[hongweiliu17]

/test appstudio-e2e-tests

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Infrastructure

Pipeline failed due to a timeout in E2E tests caused by the 'build-service-in-cluster-local' Argo CD application being in a degraded state.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e job timed out because the build-service-in-cluster-local Argo CD application was in a Degraded state. This prevented the necessary build service from initializing correctly, halting the test execution.

Contributing Factors

The build-service-controller-manager deployment within the build-service namespace also shows a Degraded health status, indicating a systemic issue with the build service's operational readiness. Furthermore, multiple Argo CD ApplicationSets are in an OutOfSync state, pointing to potential broader synchronization problems within the cluster's declarative state management. The tektonconfigs.json suggests that the TektonAddon is not ready, with errors indicating it needs to reconcile and proceed, which could be a dependency or configuration issue impacting the build service deployment.

Impact

The degraded state of the build service application directly blocked the execution of the E2E tests. As the tests could not proceed, the job eventually timed out, preventing the successful completion of the pipeline and the validation of the AppStudio infrastructure deployments.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The e2e tests timed out because the 'build-service-in-cluster-local' Argo CD application remained in a degraded state, preventing the tests from proceeding. This suggests an underlying issue with the deployment or configuration of the build service within the OpenShift cluster.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.log line 768

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

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.log line 770

build-service-in-cluster-local                      Synced   Degraded

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.log line 770

Waiting 10 seconds for application sync

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.log line 788

build-service-in-cluster-local                      Synced   Degraded

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.log line 788

Waiting 10 seconds for application sync

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.log line 1070

{"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:06:30Z"}

---

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

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

[hongweiliu17]

/test appstudio-e2e-tests