integration-service update

[rh-tap-build-team]

Included PRs:

• feat(STONEINTG-1471): snapshot GC deletes superseded Snapshots konflux-ci/integration-service#1442
• fix(STONEINTG-1475): fix for gitlab setCommitStatus konflux-ci/integration-service#1452

[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 a network-related timeout during the Helm chart download for the vector-kubearchive-log-collector component, preventing kustomize build from completing.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step timed out during the kustomize build execution for the vector-kubearchive-log-collector component. This was caused by an inability to download a required Helm chart, which was a direct result of a network connection reset.

Contributing Factors

The additional_context reveals that some ArgoCD applications, like build-service-in-cluster-local, are in a 'Degraded' state, and there are issues with certain pods being in PodInitializing or having image pull problems, as noted in the must-gather logs. These environmental issues could indicate underlying network instability or resource constraints that contributed to the Helm chart download failure. Additionally, the tektonconfigs.json shows ComponentsReady and Ready conditions as False for Tekton components, suggesting potential issues with the Tekton operator's ability to function correctly.

Impact

The timeout prevented the kustomize build process from completing successfully, which in turn blocked the execution of the end-to-end tests for the AppStudio infrastructure. This failure prevented the validation of the deployed components and thus halted the CI pipeline.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The failure is caused by a timeout during the kustomize build process for the vector-kubearchive-log-collector component, which in turn failed to download a Helm chart due to a network connection reset.

---

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

[hongweiliu17]

/approve
/lgtm

[hongweiliu17]

/retest

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Timeout

The Prow job timed out during end-to-end test execution due to underlying issues with application deployment and Tekton component readiness, preventing timely test completion.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step of the Prow job exceeded its allocated 2-hour execution time, resulting in a timeout.

Contributing Factors

Several factors likely contributed to the extended execution time:

• Argo CD ApplicationSync Issues: Multiple Argo CD ApplicationSets were found in an 'OutOfSync' or 'Missing' health status, indicating that deployments might not have been in a stable state.
• Degraded Deployment: The build-service-controller-manager Deployment was in a 'Degraded' state.
• Tekton Component Readiness: The TektonAddon and TektonConfig components reported that they were not ready, with specific issues related to openshift console resources and reconciliation needs. These underlying infrastructure readiness problems likely impacted the environment where the E2E tests were running, leading to delays.

Impact

The timeout in the E2E tests prevented the successful completion of the Prow job, which is crucial for validating infrastructure deployments. This blocked the promotion of changes and could lead to undetected issues in the application environment.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The end-to-end tests exceeded the maximum allowed execution time, resulting in a timeout. This could be due to slow test execution, resource contention, or an actual test failure preventing completion.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/pod.log line 1576

{"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-04T04:36:12Z"}

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/pod.log line 1577

{"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-04T04:36:27Z"}

---

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

[hongweiliu17]

/test appstudio-e2e-tests

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Timeout

The appstudio-e2e-tests/redhat-appstudio-e2e step in the Prow job timed out after exceeding its 2-hour execution limit, causing the entire job to fail.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step failed because it exceeded the maximum allowed execution time of 2 hours. The Prow job runner terminated the process after this time limit was reached, with a subsequent 15-second grace period also failing to result in process exit.

Contributing Factors

While not a direct cause of the timeout, the provided additional_context reveals several potential contributing factors that may have led to extended test execution times. These include:

• Multiple Argo CD ApplicationSet resources being in an OutOfSync or Missing state.
• A build-service-controller-manager Deployment being Degraded due to exceeding its progress deadline.
• TektonAddons and TektonConfig showing False for InstallerSetReady and Ready conditions due to deployment readiness issues with tkn-cli-serve.

These environmental issues suggest that the underlying cluster or the deployed applications might not be in a fully healthy or optimized state, potentially slowing down test execution or causing retries that consume more time.

Impact

The timeout of the appstudio-e2e-tests/redhat-appstudio-e2e step prevented the completion of the E2E testing phase for the AppStudio infrastructure deployments. This means that the success of the deployment for pull request #10367 could not be validated, blocking further integration or merging of the changes.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The E2E tests exceeded the maximum allowed execution time of 2 hours, causing the job to time out.

Logs:

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

{"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-04T08:31:09Z"}

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

{"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-04T08:31:24Z"}

---

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

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Timeout

The AppStudio E2E tests timed out due to an excessive execution duration, potentially caused by underlying infrastructure issues related to ApplicationSet synchronization and Tekton component readiness.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step in the Prow job exceeded the 2-hour execution timeout. This prevented the successful completion of the end-to-end test suite.

Contributing Factors

Several ApplicationSet resources are in an OutOfSync or Missing state, affecting components like application-api, crossplane-control-plane, and various monitoring and pipeline services. Additionally, the build-service-controller-manager deployment is in a Degraded state due to exceeding its progress deadline. The TektonAddon and TektonConfig resources indicate that their components are not ready, with TektonAddon citing issues with openshift console resources and the tkn-cli-serve deployment, and TektonConfig requiring reconciliation for its components. These factors likely contributed to the prolonged execution time of the E2E tests, leading to the timeout.

Impact

The timeout of the E2E test step halted the CI job, preventing the validation of the AppStudio infrastructure deployment for the given pull request. This blockage means that any potential issues or regressions in the deployed infrastructure were not detected by this job.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The end-to-end tests or the necessary setup for them exceeded the 2-hour timeout limit of the CI job.

Logs:

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

{"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-05T04:38:20Z"}

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

{"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-05T04:38:35Z"}

---

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

[hongweiliu17]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 [hongweiliu17]

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

[dirgim]

/retest

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Timeout

The AppStudio e2e tests timed out after exceeding the 2-hour execution limit, preventing the completion of the Prow job.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step of the Prow job timed out because the execution of the end-to-end tests exceeded the maximum allowed duration of 2 hours.

Contributing Factors

While the direct cause is a timeout, the additional_context reveals several potential contributing factors to the extended test execution time. The build-service-in-cluster-local Argo CD application is in a Degraded state, and multiple ApplicationSets are reported as OutOfSync or Progressing instead of Healthy and Synced. Furthermore, the Tekton Addon addon is in an Error state due to installer set issues. These conditions suggest underlying instability or performance degradation in the environment where the tests were running, which likely increased the time required for test setup, execution, and synchronization.

Impact

The timeout directly blocked the Prow job from completing successfully. Since no specific test failures were identified, the entire job run is considered a failure, and no test results or further pipeline stages could be processed.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The e2e tests exceeded the allocated timeout of 2 hours. This was likely caused by the lengthy setup and synchronization of multiple Kubernetes resources and applications, which took longer than expected, preventing the tests from completing within the time limit.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/pod.log:258

{"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-05T10:45:21Z"}

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/pod.log:267

{"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-05T10:45:36Z"}

---

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

[hongweiliu17]

/test appstudio-e2e-tests

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Infrastructure

Pipeline failed to clone the infra-deployments repository due to a DNS resolution error for github.com, which is a prerequisite for the E2E tests.

📋 Technical Details

Immediate Cause

The redhat-appstudio-e2e step failed because it could not resolve the DNS for github.com. This prevented the necessary infra-deployments repository from being cloned, which is a critical prerequisite for the E2E test execution.

Contributing Factors

Multiple other steps (gather-audit-logs, gather-extra, gather-must-gather, redhat-appstudio-gather) failed with an exec format error when attempting to execute /bin/bash. This error strongly suggests an architecture mismatch between the container image and the execution environment, indicating a potential broader infrastructure or container image configuration issue that may be affecting the environment.

Impact

The inability to clone the repository blocked the execution of the main E2E tests. The subsequent failures in data gathering steps were a consequence of the primary E2E test execution failing to initialize correctly.

🔍 Evidence

appstudio-e2e-tests/gather-audit-logs

Category: infrastructure
Root Cause: The exec format error when trying to execute /bin/bash indicates an architecture mismatch between the container image and the execution environment. The container's bash executable is not compatible with the host system's architecture.

Logs:

artifacts/appstudio-e2e-tests/gather-audit-logs/gather-audit-logs.log

could not start the process: fork/exec /bin/bash: exec format error

appstudio-e2e-tests/gather-extra

Category: infrastructure
Root Cause: The execution environment is incompatible with the binary being run, likely due to an architecture mismatch. This could be caused by trying to run a container image built for a different CPU architecture than the host machine or the execution environment.

Logs:

artifacts/appstudio-e2e-tests/gather-extra/log.txt line 1

could not start the process: fork/exec /bin/bash: exec format error

appstudio-e2e-tests/gather-must-gather

Category: infrastructure
Root Cause: The exec format error suggests that the bash executable or a script relying on it is incompatible with the underlying system architecture or operating system where the step is executing. This is likely an environment or image configuration issue.

Logs:

artifacts/appstudio-e2e-tests/gather-must-gather/log.txt line 1

could not start the process: fork/exec /bin/bash: exec format error

appstudio-e2e-tests/redhat-appstudio-e2e

Category: infrastructure
Root Cause: The job experienced a network connectivity issue, preventing it from resolving the DNS for github.com, which is necessary for cloning the infra-deployments repository.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.txt line 574

fatal: unable to access 'https://github.com/konflux-ci/e2e-tests.git/': Could not resolve host: github.com

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.txt line 573

I0206 03:18:17.455605   17454 utils.go:93] got an error: exit status 1 - will retry in 10s

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step.txt line 577

Error: error when bootstrapping cluster: reached maximum number of attempts (2). error: failed to clone infra-deployments repository: exit status 1

appstudio-e2e-tests/redhat-appstudio-gather

Category: infrastructure
Root Cause: The pipeline step failed because the underlying execution environment or container image has an architecture mismatch with the expected format for the /bin/bash executable. This prevents the shell from being launched, halting the execution of the step.

Logs:

appstudio-e2e-tests/redhat-appstudio-gather

could not start the process: fork/exec /bin/bash: exec format error

---

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

[hongweiliu17]

/test appstudio-e2e-tests

[hongweiliu17]

/test appstudio-e2e-tests

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Timeout

The end-to-end tests timed out during execution, preventing the completion of the Prow job.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step exceeded its allocated 2-hour execution timeout. The subsequent attempt to gracefully terminate the process also failed to complete within the 15-second grace period.

Contributing Factors

While the direct cause is a timeout, the additional_context reveals several underlying cluster health issues. Notably, multiple Argo CD ApplicationSets are in an OutOfSync state, the build-service-controller-manager deployment is Degraded, and Tekton configuration (tektonconfigs.json) indicates that components are not ready, specifically the TektonAddon needing reconciliation. These environmental instabilities could have led to performance degradation or blocking conditions that caused the tests to run excessively long.

Impact

The timeout of the e2e tests step halted the Prow job execution, preventing any further steps from running and thus blocking the validation of the infrastructure deployment for the given pull request.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The e2e tests or their setup procedures exceeded the maximum allowed execution time. This could be due to slow test execution, resource contention, or an infinite loop in the test or setup logic.

Logs:

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

{"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-06T08:43:26Z"}

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

{"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-06T08:43:41Z"}

---

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

[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	53cfd25	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.