./mage -v ci:teste2e Running target: CI:TestE2E I0922 05:24:46.239884 15531 magefile.go:521] setting up new custom bundle for testing... I0922 05:24:46.723478 15531 util.go:521] found credentials for image ref quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1758518686-elqd -> user: redhat-appstudio-qe+redhat_appstudio_quality Creating Tekton Bundle: - Added Pipeline: docker-build to image I0922 05:24:48.313937 15531 bundle.go:57] image digest for a new tekton bundle quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1758518686-elqd: quay.io/redhat-appstudio-qe/test-images@sha256:a146abc7dcda29fcce89527ad2306bcb2af914ba471ce2fb4b763e7b08d15ccc I0922 05:24:48.313972 15531 magefile.go:527] To use the custom docker bundle locally, run below cmd: export CUSTOM_DOCKER_BUILD_PIPELINE_BUNDLE=quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1758518686-elqd I0922 05:24:48.314006 15531 image_controller.go:49] checking if repository is image-controller I0922 05:24:48.314016 15531 build_service.go:49] checking if repository is build-service I0922 05:24:48.314023 15531 e2e_repo.go:347] checking if repository is e2e-tests I0922 05:24:48.314030 15531 release_service.go:50] checking if repository is release-service I0922 05:24:49.446857 15531 release_service_catalog.go:104] checking if repository is release-service-catalog I0922 05:24:49.446874 15531 release_service_catalog.go:70] setting test label for release-pipelines: konflux-e2e-release-catalog-staging-lsnl9 exec: go "install" "-mod=mod" "github.com/onsi/ginkgo/v2/ginkgo" go: downloading github.com/go-task/slim-sprig/v3 v3.0.0 go: downloading github.com/google/pprof v0.0.0-20241210010833-40e02aabc2ad I0922 05:24:53.215443 15531 integration_service.go:49] checking if repository is integration-service I0922 05:24:53.215472 15531 types.go:155] The following rules have matched Release-service-catalog repo CI Workflow Rule. I0922 05:24:53.215482 15531 types.go:180] Will apply rules exec: ginkgo "--seed=1758518686" "--timeout=2h30m0s" "--grace-period=30s" "--output-interceptor-mode=none" "--label-filter=konflux-e2e-release-catalog-staging-lsnl9" "--no-color" "--json-report=e2e-report.json" "--junit-report=e2e-report.xml" "--procs=20" "--nodes=20" "--p" "--output-dir=/workspace/artifact-dir" "./cmd" "--" go: downloading github.com/konflux-ci/build-service v0.0.0-20240611083846-2dee6cfe6fe4 go: downloading github.com/IBM/go-sdk-core/v5 v5.15.3 go: downloading github.com/IBM/vpc-go-sdk v0.48.0 go: downloading github.com/aws/aws-sdk-go-v2 v1.32.7 go: downloading github.com/aws/aws-sdk-go-v2/service/ec2 v1.135.0 go: downloading github.com/aws/aws-sdk-go-v2/config v1.28.7 go: downloading github.com/go-playground/validator/v10 v10.17.0 go: downloading github.com/go-openapi/strfmt v0.22.0 go: downloading github.com/google/go-github/v45 v45.2.0 go: downloading github.com/aws/smithy-go v1.22.1 go: downloading github.com/aws/aws-sdk-go-v2/credentials v1.17.48 go: downloading github.com/aws/aws-sdk-go-v2/feature/ec2/imds v1.16.22 go: downloading github.com/aws/aws-sdk-go-v2/internal/ini v1.8.1 go: downloading github.com/aws/aws-sdk-go-v2/service/sso v1.24.8 go: downloading github.com/aws/aws-sdk-go-v2/service/ssooidc v1.28.7 go: downloading github.com/aws/aws-sdk-go-v2/service/sts v1.33.3 go: downloading github.com/gabriel-vasile/mimetype v1.4.3 go: downloading github.com/go-playground/universal-translator v0.18.1 go: downloading github.com/leodido/go-urn v1.3.0 go: downloading github.com/asaskevich/govalidator v0.0.0-20230301143203-a9d515a09cc2 go: downloading github.com/go-openapi/errors v0.21.0 go: downloading github.com/mitchellh/mapstructure v1.5.0 go: downloading github.com/oklog/ulid v1.3.1 go: downloading github.com/go-playground/locales v0.14.1 go: downloading go.mongodb.org/mongo-driver v1.13.1 go: downloading github.com/aws/aws-sdk-go-v2/internal/configsources v1.3.26 go: downloading github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.6.26 go: downloading github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding v1.12.1 go: downloading github.com/aws/aws-sdk-go-v2/service/internal/presigned-url v1.12.7 Running Suite: Red Hat App Studio E2E tests - /tmp/tmp.GIlDXQqj2f/cmd ===================================================================== Random Seed: 1758518686 Will run 0 of 401 specs Running in parallel across 20 processes SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created a PipelineRun is triggered [multi-platform, aws-host-pool] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:120 ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created the build-container task from component pipelinerun is buildah-remote [multi-platform, aws-host-pool] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:124 ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created The multi platform secret is populated [multi-platform, aws-host-pool] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:127 ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created that PipelineRun completes successfully [multi-platform, aws-host-pool] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:148 ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created test that cleanup happened successfully [multi-platform, aws-host-pool] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:152 ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created a PipelineRun is triggered [multi-platform, aws-dynamic] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:251 ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created the build-container task from component pipelinerun is buildah-remote [multi-platform, aws-dynamic] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:255 ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created The multi platform secret is populated [multi-platform, aws-dynamic] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:259 ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created that PipelineRun completes successfully [multi-platform, aws-dynamic] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:263 ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created check cleanup happened successfully [multi-platform, aws-dynamic] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:267 ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created a PipelineRun is triggered [multi-platform, ibmz-dynamic] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:341 ------------------------------ SS ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created the build-container task from component pipelinerun is buildah-remote [multi-platform, ibmz-dynamic] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:345 ------------------------------ SS ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created The multi platform secret is populated [multi-platform, ibmz-dynamic] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:349 ------------------------------ SS ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created that PipelineRun completes successfully [multi-platform, ibmz-dynamic] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:353 ------------------------------ SSSS ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created check cleanup happened successfully [multi-platform, ibmz-dynamic] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:357 ------------------------------ S ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created a PipelineRun is triggered [multi-platform, ibmp-dynamic] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:432 ------------------------------ S ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created the build-container task from component pipelinerun is buildah-remote [multi-platform, ibmp-dynamic] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:436 ------------------------------ S ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created The multi platform secret is populated [multi-platform, ibmp-dynamic] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:440 ------------------------------ SSS ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created that PipelineRun completes successfully [multi-platform, ibmp-dynamic] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:444 ------------------------------ P [PENDING] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created check cleanup happened successfully [multi-platform, ibmp-dynamic] /tmp/tmp.GIlDXQqj2f/tests/build/multi-platform.go:448 ------------------------------ SSS ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params when context points to a file [build-templates] /tmp/tmp.GIlDXQqj2f/tests/build/tkn-bundle.go:177 ------------------------------ SSSSSSSSSSSSSSS ------------------------------ P [PENDING] [build-service-suite Build templates E2E test] HACBS pipelines when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build should have Pipeline Logs [build, build-templates, HACBS, pipeline-service, pipeline] /tmp/tmp.GIlDXQqj2f/tests/build/build_templates.go:478 ------------------------------ SSSSSSSSS ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles from specific context [build-templates] /tmp/tmp.GIlDXQqj2f/tests/build/tkn-bundle.go:188 ------------------------------ SSSSSSSSSSSS ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params when context is the root directory [build-templates] /tmp/tmp.GIlDXQqj2f/tests/build/tkn-bundle.go:198 ------------------------------ SSSSS ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles when context points to a file and a directory [build-templates] /tmp/tmp.GIlDXQqj2f/tests/build/tkn-bundle.go:207 ------------------------------ SSS ------------------------------ P [PENDING] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created when second component is deleted, pac pr branch should not exist in the repo [build-service, pac-build, secret-lookup] /tmp/tmp.GIlDXQqj2f/tests/build/build.go:1111 ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles when using negation [build-templates] /tmp/tmp.GIlDXQqj2f/tests/build/tkn-bundle.go:217 ------------------------------ SSSSSSSS ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params allows overriding HOME environment variable [build-templates] /tmp/tmp.GIlDXQqj2f/tests/build/tkn-bundle.go:227 ------------------------------ SSSSSSSSSSSSSS ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when a new Component is created should have a related PaC init PR created [integration-service, pipelinerun-resolution] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:77 ------------------------------ S ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params allows overriding STEP image [build-templates] /tmp/tmp.GIlDXQqj2f/tests/build/tkn-bundle.go:236 ------------------------------ SSSS ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when a new Component is created triggers a build PipelineRun [integration-service, pipelinerun-resolution] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:98 ------------------------------ SSSSSSSSSSSS ------------------------------ P [PENDING] [build-service-suite Build templates E2E test] HACBS pipelines when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta should have Pipeline Logs [build, build-templates, HACBS, pipeline-service, pipeline] /tmp/tmp.GIlDXQqj2f/tests/build/build_templates.go:478 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when a new Component is created verifies if the build PipelineRun contains the finalizer [integration-service, pipelinerun-resolution] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:103 ------------------------------ S ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for release-to-github pipeline] Release-to-github happy path Post-release verification verifies if release CR is created [release-pipelines, release-to-github, releaseToGithub] /tmp/tmp.GIlDXQqj2f/tests/release/pipelines/release_to_github.go:139 ------------------------------ SSSSSSSSS ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when a new Component is created waits for build PipelineRun to succeed [integration-service, pipelinerun-resolution] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:114 ------------------------------ SSSSSSSSS ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for release-to-github pipeline] Release-to-github happy path Post-release verification verifies the release pipelinerun is running and succeeds [release-pipelines, release-to-github, releaseToGithub] /tmp/tmp.GIlDXQqj2f/tests/release/pipelines/release_to_github.go:149 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the BuildPipelineRun have the annotation of chains signed [integration-service, pipelinerun-resolution] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:122 ------------------------------ SSSSS ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for release-to-github pipeline] Release-to-github happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, release-to-github, releaseToGithub] /tmp/tmp.GIlDXQqj2f/tests/release/pipelines/release_to_github.go:182 ------------------------------ SS ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for release-to-github pipeline] Release-to-github happy path Post-release verification verifies if the Release exists in github repo [release-pipelines, release-to-github, releaseToGithub] /tmp/tmp.GIlDXQqj2f/tests/release/pipelines/release_to_github.go:193 ------------------------------ S ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the Snapshot is created [integration-service, pipelinerun-resolution] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:126 ------------------------------ SSSSSSSS ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the Build PipelineRun got annotated with Snapshot name [integration-service, pipelinerun-resolution] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:132 ------------------------------ SSSSSS ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when the build pipelineRun run succeeded verifies that the finalizer has been removed from the build pipelinerun [integration-service, pipelinerun-resolution] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:136 ------------------------------ SSSSSS ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if all of the integrationPipelineRuns passed [integration-service, pipelinerun-resolution, slow] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:149 ------------------------------ SSSSSSSS ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the passed status of integration test is reported in the Snapshot [integration-service, pipelinerun-resolution] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:153 ------------------------------ SSSSSS ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the finalizer was removed from all of the related Integration pipelineRuns [integration-service, pipelinerun-resolution] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:169 ------------------------------ SSSSSS ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when integration pipelineRun is created it passes, annotations and labels not overwritten by integration service checks integration pipelineRun passed [integration-service, pipelinerun-resolution] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:176 ------------------------------ SSSS ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when integration pipelineRun is created it passes, annotations and labels not overwritten by integration service verifies that existing labels and annotations are not overwritten by integration service [integration-service, pipelinerun-resolution] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:180 ------------------------------ SSSSS ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when integration pipelineRun is created it passes, annotations and labels not overwritten by integration service verifies that PipelinesAsCode specific annotations with dynamic values are preserved [integration-service, pipelinerun-resolution] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:226 ------------------------------ SSSS ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when integration pipelineRun is created it passes, annotations and labels not overwritten by integration service verifies that ResolutionRequest is deleted after pipeline resolution [integration-service, pipelinerun-resolution] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:263 ------------------------------ SSS ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when integration pipelineRun is created it passes, annotations and labels not overwritten by integration service verifies that no orphaned ResolutionRequests remain in namespace after test completion [integration-service, pipelinerun-resolution] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:287 ------------------------------ SSSS ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when integration pipelineRun is created it passes, annotations and labels not overwritten by integration service validates that second integration pipelineRun failed due to resolution not pipelinerun [integration-service, pipelinerun-resolution] /tmp/tmp.GIlDXQqj2f/tests/integration-service/pipelinerun-resolution.go:320 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS Ran 0 of 401 Specs in 0.611 seconds SUCCESS! -- 0 Passed | 0 Failed | 51 Pending | 350 Skipped Ginkgo ran 1 suite in 1m34.113144213s Test Suite Passed