[KFLUXDP-711] Add prow-failure-analysis to the appstudio-e2etests in infra-deployments tests

[calebevans]

No description provided.

[calebevans]

/pj-rehearse

[openshift-ci-robot]

@calebevans: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[calebevans]

/pj-rehearse

[openshift-ci-robot]

@calebevans: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[calebevans]

/pj-rehearse

[openshift-ci-robot]

@calebevans: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[calebevans]

/pj-rehearse

[openshift-ci-robot]

@calebevans: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[calebevans]

/pj-rehearse

[openshift-ci-robot]

@calebevans: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[calebevans]

/pj-rehearse

[openshift-ci-robot]

@calebevans: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Unknown

RCA generation failed: litellm.BadRequestError: LLM Provider NOT provided. Pass in the LLM provider you are trying to call. You passed model=google/gemini-2.5-flash-lite
Pass model as E.g. For 'Huggingface' inference endpoints pass in completion(model='huggingface/starcoder',..) Learn more: https://docs.litellm.ai/docs/providers

📋 Technical Details

Unable to generate detailed analysis.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: unknown
Root Cause: Analysis failed: litellm.BadRequestError: LLM Provider NOT provided. Pass in the LLM provider you are trying to call. You passed model=google/gemini-2.5-flash-lite
Pass model as E.g. For 'Huggingface' inference endpoints pass in completion(model='huggingface/starcoder',..) Learn more: https://docs.litellm.ai/docs/providers

---

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

[flacatus]

@calebevans Lets say we have multiple prow errors in the PR... We will see multiple bot responses errors? If yes, we should make the bot only keep the last job failure

[calebevans]

@calebevans Lets say we have multiple prow errors in the PR... We will see multiple bot responses errors? If yes, we should make the bot only keep the last job failure

@flacatus If a failure occurs, it will leave a comment. If the user re-tests and it fails again, a new comment will be made with a completely new analysis where only the new failure is taken into consideration. I'm not sure that we should be deleting old comments, just so there can be a running history of failures in a PR with reasons for why it failed.

[calebevans]

/pj-rehearse

[openshift-ci-robot]

@calebevans: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@calebevans: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-redhat-appstudio-infra-deployments-main-appstudio-e2e-tests	redhat-appstudio/infra-deployments	presubmit	Ci-operator config changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Infrastructure

The pipeline failed due to a GitLab API request timeout during the e2e test execution, preventing the creation of necessary build artifacts.

📋 Technical Details

Immediate Cause

A GitLab API request timed out with a 408 Request Timeout error. This prevented the appstudio-e2e-tests/redhat-appstudio-e2e step from successfully creating a Dockerfile and YAML manifest, which are essential for subsequent build and distribution operations.

Contributing Factors

The test Red Hat App Studio E2E tests.[It] [build-service-suite Build service E2E tests] test of component update with renovate gitlab when components are created in same namespace create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component] explicitly failed because the underlying GitLab API call to fetch merge requests timed out. This suggests a potential network instability or GitLab server-side issue that affected the test environment.

Impact

The GitLab API timeout directly blocked the completion of a core e2e test scenario, preventing the validation of build service functionality with renovate and multi-component setups. This failure prevented the pipeline from proceeding with further validation or deployment steps.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: infrastructure
Root Cause: The failure was caused by a GitLab API request timing out (408 Request Timeout), preventing the test from completing the creation of a Dockerfile and YAML manifest, and subsequently impacting dependent test cases.

---

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

[calebevans]

/pj-rehearse

[openshift-ci-robot]

@calebevans: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[calebevans]

/pj-rehearse skip

[openshift-ci-robot]

@calebevans: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: calebevans, psturc

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:

• ci-operator/config/redhat-appstudio/infra-deployments/OWNERS [psturc]
• ci-operator/step-registry/prow-failure-analysis/OWNERS [calebevans,psturc]
• ci-operator/step-registry/redhat-appstudio/OWNERS [psturc]

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

[calebevans]

/pj-rehearse abort

[openshift-ci-robot]

@calebevans: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Test

The E2E tests failed due to a violation of enterprise contract policies, specifically reporting "No test data found" during the verification step.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e job failed because the verify-enterprise-contract Tekton task within it could not find the expected test data for enterprise contract policy verification, resulting in a failure to meet policy requirements.

Contributing Factors

None identified in the provided data.

Impact

This failure prevented the successful completion of the E2E test suite, indicating a potential issue with test data setup or policy enforcement within the test environment.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: test
Root Cause: The E2E test failed due to a specific enterprise contract policy violation: "No test data found" in the verify-enterprise-contract Tekton task. This occurred during a test case designed to fail when policy checks are not met, indicating a potential issue with how test results are being generated or reported within the test pipeline.

---

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