fix: remove simple build dependency from tests

[tisutisu]

Description

This PR includes changes to remove dependency on simple build from test suites

Issue ticket number and link

https://issues.redhat.com/browse/STONEBLD-2611

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Checklist:

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
• I have updated labels (if needed)

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from tisutisu. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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]

@tisutisu: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name	Command
konflux-e2e-v9fpx-c4sq6	/retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-v9fpx-c4sq6

For instructions on how to install ORAS, please refer to the ORAS installation guide.

[konflux-ci-qe-bot]

@tisutisu: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name	Command
konflux-e2e-qxwln-lmm4k	/retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-qxwln-lmm4k

For instructions on how to install ORAS, please refer to the ORAS installation guide.

[konflux-ci-qe-bot]

@tisutisu: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name	Command
konflux-e2e-929fb-rtx76	/retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-929fb-rtx76

For instructions on how to install ORAS, please refer to the ORAS installation guide.

[konflux-ci-qe-bot]

@tisutisu: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name	Command
konflux-e2e-cw5nr-cx6qc	/retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-cw5nr-cx6qc

For instructions on how to install ORAS, please refer to the ORAS installation guide.

[konflux-ci-qe-bot]

@tisutisu: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name	Command
konflux-e2e-9pmn4-gjkhm	/retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-9pmn4-gjkhm

For instructions on how to install ORAS, please refer to the ORAS installation guide.

[openshift-ci]

🚨 Error occurred while running the E2E tests, list of failed Spec(s):

• ➡️ [panicked] [It] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification verifies that Component 1 can be created and build PipelineRun is created for it in dev namespace and succeeds [release-pipelines, pushPyxis]

runtime error: invalid memory address or nil pointer dereference

• ➡️ [failed] [It] [release-pipelines-suite e2e tests for release-to-github pipeline] Release-to-github happy path Post-release verification verifies release pipelinerun is running and succeeds [release-pipelines, release-to-github, releaseToGithub]

Unexpected error:
    <*errors.errorString | 0xc00187cde0>: 
    could not find Release CR based on associated Snapshot 'samp-app-zemb-dwjmp' in 'dev-release-team-tenant' namespace
    {
        s: "could not find Release CR based on associated Snapshot 'samp-app-zemb-dwjmp' in 'dev-release-team-tenant' namespace",
    }
occurred

• ➡️ [failed] [It] [release-pipelines-suite e2e tests for rh-push-to-redhat-io pipeline] Rh-push-to-redhat-io happy path Post-release verification verifies the rhio release pipelinerun is running and succeeds [release-pipelines, rh-push-to-redhat-io, PushToRedhatIO]

Unexpected error:
    <*errors.errorString | 0xc0013b20a0>: 
    could not find Release CR based on associated Snapshot 'rhio-app-ifqz-mjqn4' in 'dev-release-team-tenant' namespace
    {
        s: "could not find Release CR based on associated Snapshot 'rhio-app-ifqz-mjqn4' in 'dev-release-team-tenant' namespace",
    }
occurred

• ➡️ [failed] [It] [release-pipelines-suite e2e tests for rh-advisories pipeline] Rh-advisories happy path Post-release verification verifies the advs release pipelinerun is running and succeeds [release-pipelines, rh-advisories, rhAdvisories]

Unexpected error:
    <*errors.errorString | 0xc000b50720>: 
    could not find Release CR based on associated Snapshot 'advs-app-htty-c8xhg' in 'dev-release-team-tenant' namespace
    {
        s: "could not find Release CR based on associated Snapshot 'advs-app-htty-c8xhg' in 'dev-release-team-tenant' namespace",
    }
occurred

• ➡️ [failed] [It] [release-pipelines-suite e2e tests for rhtap-service-push pipeline] Rhtap-service-push happy path Post-release verification verifies the rhtap release pipelinerun is running and succeeds [release-pipelines, rhtap-service-push, RhtapServicePush]

Unexpected error:
    <*errors.errorString | 0xc00109af30>: 
    could not find Release CR based on associated Snapshot 'rhtap-app-bmng-gtv64' in 'dev-release-team-tenant' namespace
    {
        s: "could not find Release CR based on associated Snapshot 'rhtap-app-bmng-gtv64' in 'dev-release-team-tenant' namespace",
    }
occurred

• ➡️ [failed] [It] [release-service-suite Release service tenant pipeline] Post-release verification verifies that a Release CR should have been created in the dev namespace [release-pipelines, tenant]

Timed out after 300.000s.
Expected success, but got an error:
    <*errors.errorString | 0xc001222fe0>: 
    could not find any Releases in namespace tenant-dev-blmh-tenant: <nil>
    {
        s: "could not find any Releases in namespace tenant-dev-blmh-tenant: <nil>",
    }

• ➡️ [failed] [It] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-tests, fbcHappyPath]

Timed out after 300.014s.
timed out when waiting for Snapshot and Release being created
Expected success, but got an error:
    <*errors.errorString | 0xc0018504a0>: 
    could not find Release CR based on associated Snapshot 'fbc-pipelines-app-lnwh-mw6c7' in 'dev-release-team-tenant' namespace
    {
        s: "could not find Release CR based on associated Snapshot 'fbc-pipelines-app-lnwh-mw6c7' in 'dev-release-team-tenant' namespace",
    }

• ➡️ [failed] [It] [release-pipelines-suite Push to external registry] Post-release verification verifies that a build PipelineRun is created in dev namespace and succeeds [release-pipelines, push-to-external-registry]

Expected success, but got an error:
    <*errors.errorString | 0xc0008ba440>: 
    PipelineRun cannot be created for the Component ex-registry-vekp-tenant/dc-metro-map
    {
        s: "PipelineRun cannot be created for the Component ex-registry-vekp-tenant/dc-metro-map",
    }

🙈 Link to Pod logs.
🙉 Link to Custom Resources.
🙊 Link to junit-summary.html.

---

@tisutisu: 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/redhat-appstudio-e2e	79ce1a5	link	true	/test redhat-appstudio-e2e

Full PR test history. Your PR dashboard.

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.

[tisutisu]

/hold

[konflux-ci-qe-bot]

@tisutisu: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name	Command
konflux-e2e-zdjkq-sbq2q	/retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-zdjkq-sbq2q

For instructions on how to install ORAS, please refer to the ORAS installation guide.

[openshift-merge-robot]

PR needs rebase.

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.