./mage -v ci:teste2e Running target: CI:TestE2E I0417 07:02:45.058478 18018 magefile.go:529] setting up new custom bundle for testing... I0417 07:02:45.527315 18018 util.go:512] found credentials for image ref quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1776409365-tqcc -> user: redhat-appstudio-qe+redhat_appstudio_quality Creating Tekton Bundle: - Added Pipeline: docker-build to image I0417 07:02:46.703078 18018 bundle.go:57] image digest for a new tekton bundle quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1776409365-tqcc: quay.io/redhat-appstudio-qe/test-images@sha256:941afedb73976e5ec0b558864b4fa583047ac8820de46d3091a77f66873b6570 I0417 07:02:46.703119 18018 magefile.go:535] 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-1776409365-tqcc I0417 07:02:46.703157 18018 build_service.go:50] checking if repository is build-service I0417 07:02:46.703167 18018 build_service.go:31] require sprayproxy registering is set to TRUE I0417 07:02:46.703175 18018 build_service.go:34] setting test label filter: 'build-service' 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-20260106004452-d7df1bf2cac7 I0417 07:02:50.292170 18018 e2e_repo.go:347] checking if repository is e2e-tests I0417 07:02:50.292193 18018 release_service.go:50] checking if repository is release-service I0417 07:02:51.416826 18018 release_service_catalog.go:104] checking if repository is release-service-catalog I0417 07:02:51.416847 18018 integration_service.go:49] checking if repository is integration-service I0417 07:02:51.416852 18018 image_controller.go:49] checking if repository is image-controller I0417 07:02:51.416859 18018 types.go:155] The following rules have matched build-service repo CI Workflow Rule. I0417 07:02:51.416864 18018 types.go:180] Will apply rules exec: ginkgo "--seed=1776409365" "--timeout=1h30m0s" "--grace-period=30s" "--output-interceptor-mode=none" "--label-filter=build-service" "--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/minio/minio-go/v7 v7.0.99 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.41.3 go: downloading github.com/aws/aws-sdk-go-v2/config v1.31.3 go: downloading github.com/aws/aws-sdk-go-v2/service/ec2 v1.143.0 go: downloading github.com/minio/crc64nvme v1.1.1 go: downloading github.com/dustin/go-humanize v1.0.1 go: downloading github.com/klauspost/crc32 v1.3.0 go: downloading github.com/minio/md5-simd v1.1.2 go: downloading github.com/rs/xid v1.6.0 go: downloading github.com/go-ini/ini v1.67.0 go: downloading github.com/tinylib/msgp v1.6.1 go: downloading github.com/go-playground/validator/v10 v10.17.0 go: downloading github.com/go-openapi/strfmt v0.23.0 go: downloading github.com/aws/smithy-go v1.24.2 go: downloading github.com/aws/aws-sdk-go-v2/credentials v1.18.7 go: downloading github.com/aws/aws-sdk-go-v2/service/ssooidc v1.34.0 go: downloading github.com/aws/aws-sdk-go-v2/internal/ini v1.8.3 go: downloading github.com/aws/aws-sdk-go-v2/service/sso v1.28.2 go: downloading github.com/aws/aws-sdk-go-v2/feature/ec2/imds v1.18.4 go: downloading github.com/aws/aws-sdk-go-v2/service/sts v1.38.0 go: downloading go.mongodb.org/mongo-driver v1.17.4 go: downloading github.com/go-openapi/errors v0.22.2 go: downloading github.com/mitchellh/mapstructure v1.5.1-0.20231216201459-8508981c8b6c go: downloading github.com/asaskevich/govalidator v0.0.0-20230301143203-a9d515a09cc2 go: downloading github.com/oklog/ulid v1.3.1 go: downloading github.com/philhofer/fwd v1.2.0 go: downloading github.com/google/go-github/v45 v45.2.0 go: downloading github.com/leodido/go-urn v1.3.0 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/go-playground/locales v0.14.1 go: downloading github.com/aws/aws-sdk-go-v2/internal/configsources v1.4.19 go: downloading github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.7.19 go: downloading github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding v1.13.6 go: downloading github.com/aws/aws-sdk-go-v2/service/internal/presigned-url v1.13.19 Running Suite: Red Hat App Studio E2E tests - /tmp/tmp.yHGHPgvWPm/cmd ===================================================================== Random Seed: 1776409365 Will run 150 of 464 specs Running in parallel across 20 processes SSS ------------------------------ P [PENDING] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification creates component from git source https://github.com/redhat-appstudio-qe/fbc-sample-repo-test [release-pipelines, fbc-release, fbcHappyPath] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/fbc_release.go:123 ------------------------------ P [PENDING] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification Creates a push snapshot for a release [release-pipelines, fbc-release, fbcHappyPath] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/fbc_release.go:128 ------------------------------ P [PENDING] [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-release, fbcHappyPath] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/fbc_release.go:132 ------------------------------ P [PENDING] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, fbc-release, fbcHappyPath] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/fbc_release.go:136 ------------------------------ P [PENDING] [release-pipelines-suite FBC e2e-tests] with FBC Staged Index Post-release verification creates component from git source https://github.com/redhat-appstudio-qe/fbc-sample-repo-test [release-pipelines, fbc-release, fbcStagedIndex] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/fbc_release.go:178 ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for rhtap-service-push pipeline] Rhtap-service-push happy path Post-release verification verifies if the release CR is created [release-pipelines, rhtap-service-push, RhtapServicePush] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rhtap_service_push.go:150 ------------------------------ P [PENDING] [release-pipelines-suite FBC e2e-tests] with FBC Staged Index Post-release verification Creates a push snapshot for a release [release-pipelines, fbc-release, fbcStagedIndex] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/fbc_release.go:183 ------------------------------ S ------------------------------ P [PENDING] [release-pipelines-suite FBC e2e-tests] with FBC Staged Index Post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-release, fbcStagedIndex] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/fbc_release.go:187 ------------------------------ P [PENDING] [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] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rhtap_service_push.go:160 ------------------------------ 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.yHGHPgvWPm/tests/build/multi-platform.go:120 ------------------------------ P [PENDING] [release-pipelines-suite FBC e2e-tests] with FBC Staged Index Post-release verification verifies release CR completed and set succeeded. [release-pipelines, fbc-release, fbcStagedIndex] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/fbc_release.go:191 ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for rhtap-service-push pipeline] Rhtap-service-push happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, rhtap-service-push, RhtapServicePush] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rhtap_service_push.go:190 ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for rhtap-service-push pipeline] Rhtap-service-push happy path Post-release verification verifies if the PR in infra-deployments repo is created/updated [release-pipelines, rhtap-service-push, RhtapServicePush] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rhtap_service_push.go:200 ------------------------------ P [PENDING] [release-pipelines-suite FBC e2e-tests] with FBC hotfix process FBC hotfix post-release verification creates component from git source https://github.com/redhat-appstudio-qe/fbc-sample-repo-test [release-pipelines, fbc-release, fbcHotfix] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/fbc_release.go:233 ------------------------------ S ------------------------------ 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.yHGHPgvWPm/tests/build/multi-platform.go:124 ------------------------------ P [PENDING] [release-pipelines-suite FBC e2e-tests] with FBC hotfix process FBC hotfix post-release verification Creates a push snapshot for a release [release-pipelines, fbc-release, fbcHotfix] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/fbc_release.go:238 ------------------------------ 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.yHGHPgvWPm/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.yHGHPgvWPm/tests/build/multi-platform.go:148 ------------------------------ P [PENDING] [release-pipelines-suite FBC e2e-tests] with FBC hotfix process FBC hotfix post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-release, fbcHotfix] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/fbc_release.go:242 ------------------------------ S ------------------------------ 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.yHGHPgvWPm/tests/build/multi-platform.go:152 ------------------------------ P [PENDING] [release-pipelines-suite FBC e2e-tests] with FBC hotfix process FBC hotfix post-release verification verifies release CR completed and set succeeded. [release-pipelines, fbc-release, fbcHotfix] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/fbc_release.go:246 ------------------------------ S ------------------------------ 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.yHGHPgvWPm/tests/build/multi-platform.go:251 ------------------------------ P [PENDING] [release-pipelines-suite FBC e2e-tests] with FBC pre-GA process FBC pre-GA post-release verification creates component from git source https://github.com/redhat-appstudio-qe/fbc-sample-repo-test [release-pipelines, fbc-release, fbcPreGA] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/fbc_release.go:286 ------------------------------ 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.yHGHPgvWPm/tests/build/multi-platform.go:255 ------------------------------ S ------------------------------ P [PENDING] [release-pipelines-suite FBC e2e-tests] with FBC pre-GA process FBC pre-GA post-release verification Creates a push snapshot for a release [release-pipelines, fbc-release, fbcPreGA] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/fbc_release.go:291 ------------------------------ 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.yHGHPgvWPm/tests/build/multi-platform.go:259 ------------------------------ P [PENDING] [release-pipelines-suite FBC e2e-tests] with FBC pre-GA process FBC pre-GA post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-release, fbcPreGA] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/fbc_release.go:295 ------------------------------ SSS ------------------------------ P [PENDING] [release-pipelines-suite FBC e2e-tests] with FBC pre-GA process FBC pre-GA post-release verification verifies release CR completed and set succeeded. [release-pipelines, fbc-release, fbcPreGA] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/fbc_release.go:299 ------------------------------ 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.yHGHPgvWPm/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.yHGHPgvWPm/tests/build/multi-platform.go:267 ------------------------------ SS ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for rh-push-to-redhat-io pipeline] Rh-push-to-redhat-io happy path Post-release verification verifies if the release CR is created [release-pipelines, rh-push-to-registry-redhat-io, PushToRedhatIO] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rh_push_to_registry_redhat_io.go:108 ------------------------------ SSS ------------------------------ P [PENDING] [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-registry-redhat-io, PushToRedhatIO] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rh_push_to_registry_redhat_io.go:118 ------------------------------ 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.yHGHPgvWPm/tests/build/multi-platform.go:341 ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for rh-push-to-redhat-io pipeline] Rh-push-to-redhat-io happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, rh-push-to-registry-redhat-io, PushToRedhatIO] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rh_push_to_registry_redhat_io.go:148 ------------------------------ S ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for rh-push-to-redhat-io pipeline] Rh-push-to-redhat-io happy path Post-release verification verifies if the MR URL is valid [release-pipelines, rh-push-to-registry-redhat-io, PushToRedhatIO] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rh_push_to_registry_redhat_io.go:159 ------------------------------ 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 the build-container task from component pipelinerun is buildah-remote [multi-platform, ibmz-dynamic] /tmp/tmp.yHGHPgvWPm/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.yHGHPgvWPm/tests/build/multi-platform.go:349 ------------------------------ SSS ------------------------------ 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.yHGHPgvWPm/tests/build/multi-platform.go:353 ------------------------------ 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.yHGHPgvWPm/tests/build/multi-platform.go:357 ------------------------------ SSSS ------------------------------ 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.yHGHPgvWPm/tests/build/multi-platform.go:432 ------------------------------ 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.yHGHPgvWPm/tests/build/multi-platform.go:436 ------------------------------ SS ------------------------------ 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.yHGHPgvWPm/tests/build/multi-platform.go:440 ------------------------------ 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 that PipelineRun completes successfully [multi-platform, ibmp-dynamic] /tmp/tmp.yHGHPgvWPm/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.yHGHPgvWPm/tests/build/multi-platform.go:448 ------------------------------ S ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies the release CR is created [release-pipelines, rh-advisories, multiarch-advisories, multiArchAdvisories] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/multiarch_advisories.go:112 ------------------------------ S ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies the multiarch release pipelinerun is running and succeeds [release-pipelines, rh-advisories, multiarch-advisories, multiArchAdvisories] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/multiarch_advisories.go:122 ------------------------------ S ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, rh-advisories, multiarch-advisories, multiArchAdvisories] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/multiarch_advisories.go:152 ------------------------------ SSS ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies if the repository URL is valid [release-pipelines, rh-advisories, multiarch-advisories, multiArchAdvisories] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/multiarch_advisories.go:163 ------------------------------ SS ------------------------------ P [PENDING] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification tests that Release CR is created for the Snapshot [release-pipelines, rh-push-to-external-registry] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rh_push_to_external_registry.go:215 ------------------------------ SS ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for rh-advisories pipeline] Rh-advisories happy path Post-release verification verifies if release CR is created [release-pipelines, rh-advisories, rhAdvisories] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rh_advisories.go:117 ------------------------------ S ------------------------------ P [PENDING] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification verifies a release PipelineRun is started and succeeded in managed namespace [release-pipelines, rh-push-to-external-registry] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rh_push_to_external_registry.go:226 ------------------------------ SSSSS ------------------------------ P [PENDING] [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] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rh_advisories.go:127 ------------------------------ SS ------------------------------ P [PENDING] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification validate the result of task create-pyxis-image contains image ids [release-pipelines, rh-push-to-external-registry] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rh_push_to_external_registry.go:233 ------------------------------ P [PENDING] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification tests that Release CR has completed [release-pipelines, rh-push-to-external-registry] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rh_push_to_external_registry.go:248 ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for rh-advisories pipeline] Rh-advisories happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, rh-advisories, rhAdvisories] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rh_advisories.go:157 ------------------------------ SSSS ------------------------------ P [PENDING] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification validates that imageIds from task create-pyxis-image exist in Pyxis. [release-pipelines, rh-push-to-external-registry] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rh_push_to_external_registry.go:265 ------------------------------ SSS ------------------------------ P [PENDING] [release-pipelines-suite e2e tests for rh-advisories pipeline] Rh-advisories happy path Post-release verification verifies if the repository URL is valid [release-pipelines, rh-advisories, rhAdvisories] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/rh_advisories.go:168 ------------------------------ SSSSSSS ------------------------------ 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.yHGHPgvWPm/tests/release/pipelines/release_to_github.go:138 ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params when context points to a file [build-templates] /tmp/tmp.yHGHPgvWPm/tests/build/tkn-bundle.go:188 ------------------------------ SS ------------------------------ 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.yHGHPgvWPm/tests/release/pipelines/release_to_github.go:148 ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles from specific context [build-templates] /tmp/tmp.yHGHPgvWPm/tests/build/tkn-bundle.go:199 ------------------------------ S ------------------------------ 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.yHGHPgvWPm/tests/release/pipelines/release_to_github.go:181 ------------------------------ S ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params when context is the root directory [build-templates] /tmp/tmp.yHGHPgvWPm/tests/build/tkn-bundle.go:209 ------------------------------ 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.yHGHPgvWPm/tests/release/pipelines/release_to_github.go:192 ------------------------------ S ------------------------------ P [PENDING] [release-pipelines-suite Push to external registry] Post-release verification verifies that a Release CR should have been created in the dev namespace [release-pipelines, push-to-external-registry] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/push_to_external_registry.go:157 ------------------------------ 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.yHGHPgvWPm/tests/build/tkn-bundle.go:218 ------------------------------ S ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles when using negation [build-templates] /tmp/tmp.yHGHPgvWPm/tests/build/tkn-bundle.go:228 ------------------------------ SSSSSS ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params allows overriding HOME environment variable [build-templates] /tmp/tmp.yHGHPgvWPm/tests/build/tkn-bundle.go:238 ------------------------------ SSSSS ------------------------------ P [PENDING] [release-pipelines-suite Push to external registry] Post-release verification verifies that Release PipelineRun should eventually succeed [release-pipelines, push-to-external-registry] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/push_to_external_registry.go:164 ------------------------------ SSSSS ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params allows overriding STEP image [build-templates] /tmp/tmp.yHGHPgvWPm/tests/build/tkn-bundle.go:247 ------------------------------ S ------------------------------ P [PENDING] [release-pipelines-suite Push to external registry] Post-release verification tests if the image was pushed to quay [release-pipelines, push-to-external-registry] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/push_to_external_registry.go:168 ------------------------------ SS ------------------------------ P [PENDING] [release-pipelines-suite Push to external registry] Post-release verification verifies that a Release is marked as succeeded. [release-pipelines, push-to-external-registry] /tmp/tmp.yHGHPgvWPm/tests/release/pipelines/push_to_external_registry.go:175 ------------------------------ SSSSSSSSSSSSSSSSSSSSSS ------------------------------ P [PENDING] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) 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.yHGHPgvWPm/tests/build/build_templates.go:507 ------------------------------ SSSSSSSSSSS ------------------------------ P [PENDING] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry verify-enterprise-contract check should pass [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e] /tmp/tmp.yHGHPgvWPm/tests/build/build_templates.go:569 ------------------------------ SSSSSSSS ------------------------------ P [PENDING] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) build-definitions ec pipelines runs ec pipeline pipelines/enterprise-contract.yaml [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e] /tmp/tmp.yHGHPgvWPm/tests/build/build_templates.go:744 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ P [PENDING] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) 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.yHGHPgvWPm/tests/build/build_templates.go:507 ------------------------------ SSSSS ------------------------------ P [PENDING] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry verify-enterprise-contract check should pass [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e] /tmp/tmp.yHGHPgvWPm/tests/build/build_templates.go:569 ------------------------------ SSSSS ------------------------------ P [PENDING] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) build-definitions ec pipelines runs ec pipeline pipelines/enterprise-contract.yaml [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e] /tmp/tmp.yHGHPgvWPm/tests/build/build_templates.go:744 ------------------------------ SSSSSSSSSSSSSSSSSSSS ------------------------------ P [PENDING] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) 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-min should have Pipeline Logs [build, build-templates, HACBS, pipeline-service, pipeline] /tmp/tmp.yHGHPgvWPm/tests/build/build_templates.go:507 ------------------------------ SSS ------------------------------ P [PENDING] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry verify-enterprise-contract check should pass [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e] /tmp/tmp.yHGHPgvWPm/tests/build/build_templates.go:569 ------------------------------ SSSSS ------------------------------ P [PENDING] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) build-definitions ec pipelines runs ec pipeline pipelines/enterprise-contract.yaml [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e] /tmp/tmp.yHGHPgvWPm/tests/build/build_templates.go:744 ------------------------------ SSSSSSSSSS••••••••••••••••••••••••••••••••••••••••••••••••••• ------------------------------ 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, github, pac-build, secret-lookup] /tmp/tmp.yHGHPgvWPm/tests/build/secret_lookup.go:206 ------------------------------ ••••••••••• ------------------------------ • [FAILED] [693.916 seconds] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace [It] the PipelineRun should eventually finish successfully for parent component [build-service, renovate, multi-component, gitlab] /tmp/tmp.yHGHPgvWPm/tests/build/renovate.go:274 Timeline >> PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w found for Component build-e2e-xpjq/gl-multi-component-parent-qpia PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Running PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Running PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Running PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Running PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Running PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Running PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Running PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Running PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Running PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Running PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Running PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Running PipelineRun has not been created yet for the Component build-e2e-xpjq/gl-multi-component-parent-qpia PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Running PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Running PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Running PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Running PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: PipelineRunStopping PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: PipelineRunStopping PipelineRun gl-multi-component-parent-qpia-on-pull-request-9cc7w reason: Failed failed to get logs for PipelineRun build-e2e-xpjq:gl-multi-component-parent-qpia-on-pull-request-9cc7w: Get "https://52.89.93.242:6443/api/v1/namespaces/build-e2e-xpjq/pods/gl-multi-component-parent-qpia-on-pull-request-9cc7w-init-pod/log?container=prepare": dial tcp 52.89.93.242:6443: connect: connection refused attempt 1/3: PipelineRun "gl-multi-component-parent-qpia-on-pull-request-9cc7w" failed: pod: gl-multi-component-parent-qpia-on-pull-request-9cc7w-init-pod | init container: prepare [FAILED] in [It] - /tmp/tmp.yHGHPgvWPm/tests/build/renovate.go:276 @ 04/17/26 07:17:01.519 [FAILED] in [AfterAll] - /tmp/tmp.yHGHPgvWPm/tests/build/renovate.go:230 @ 04/17/26 07:19:01.52 failed to list pods in namespace build-service: Get "https://52.89.93.242:6443/api/v1/namespaces/build-service/pods": dial tcp 52.89.93.242:6443: connect: connection refused << Timeline [FAILED] Expected success, but got an error: <*errors.errorString | 0xc0016c8010>: failed to delete PipelineRun "gl-multi-component-parent-qpia-on-pull-request-9cc7w" from "build-e2e-xpjq" namespace with error: Delete "https://52.89.93.242:6443/apis/tekton.dev/v1/namespaces/build-e2e-xpjq/pipelineruns/gl-multi-component-parent-qpia-on-pull-request-9cc7w": dial tcp 52.89.93.242:6443: connect: connection refused { s: "failed to delete PipelineRun \"gl-multi-component-parent-qpia-on-pull-request-9cc7w\" from \"build-e2e-xpjq\" namespace with error: Delete \"https://52.89.93.242:6443/apis/tekton.dev/v1/namespaces/build-e2e-xpjq/pipelineruns/gl-multi-component-parent-qpia-on-pull-request-9cc7w\": dial tcp 52.89.93.242:6443: connect: connection refused", } In [It] at: /tmp/tmp.yHGHPgvWPm/tests/build/renovate.go:276 @ 04/17/26 07:17:01.519 There were additional failures detected. To view them in detail run ginkgo -vv ------------------------------ SSSSSSSSSSS••••••••••• ------------------------------ • [FAILED] [1835.322 seconds] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace [It] PR merge triggers PAC PipelineRun for parent component [build-service, renovate, multi-component, github] /tmp/tmp.yHGHPgvWPm/tests/build/renovate.go:385 Timeline >> Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx Push PipelineRun has not been created yet for the component build-e2e-awdm/gh-multi-component-parent-kjjx [FAILED] in [It] - /tmp/tmp.yHGHPgvWPm/tests/build/renovate.go:398 @ 04/17/26 07:45:52.871 << Timeline [FAILED] Timed out after 1800.000s. timed out when waiting for the PipelineRun to start for the component build-e2e-awdm/gh-multi-component-parent-kjjx Expected success, but got an error: <*errors.errorString | 0xc0007b8f20>: no pipelinerun found for component gh-multi-component-parent-kjjx { s: "no pipelinerun found for component gh-multi-component-parent-kjjx", } In [It] at: /tmp/tmp.yHGHPgvWPm/tests/build/renovate.go:398 @ 04/17/26 07:45:52.871 ------------------------------ SSSS ------------------------------ • [FAILED] [3344.667 seconds] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] the PipelineRun should eventually finish successfully for parent component [build-service, renovate, multi-component, forgejo] /tmp/tmp.yHGHPgvWPm/tests/build/renovate.go:274 Timeline >> PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs found for Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: PipelineRunStopping PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-hlfvs reason: Failed attempt 1/3: PipelineRun "fj-multi-component-parent-flrm-on-pull-request-hlfvs" failed: pod: fj-multi-component-parent-flrm-on-pull-request-hlfvs-init-pod | init container: prepare 2026/04/17 07:08:07 Entrypoint initialization pod: fj-multi-component-parent-flrm-on-pull-request-hlfvs-init-pod | container step-init: time="2026-04-17T07:08:11Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-17T07:08:11Z" level=info msg="[param] enable: false" time="2026-04-17T07:08:11Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-17T07:08:11Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-17T07:08:11Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-17T07:08:11Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-17T07:08:11Z" level=info msg="Cache proxy is disabled in param or in backend" time="2026-04-17T07:08:11Z" level=info msg="[result] HTTP PROXY: " time="2026-04-17T07:08:11Z" level=info msg="[result] NO PROXY: " New PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 found after retrigger for component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 found for Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun has not been created yet for the Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-flrm-on-pull-request-cvxh2 reason: Failed attempt 2/3: PipelineRun "fj-multi-component-parent-flrm-on-pull-request-cvxh2" failed: pod: fj-multi-component-parent-flrm-on-pull-request-cvxh2-init-pod | init container: prepare 2026/04/17 07:14:56 Entrypoint initialization pod: fj-multi-component-parent-flrm-on-pull-request-cvxh2-init-pod | container step-init: time="2026-04-17T07:15:01Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-17T07:15:01Z" level=info msg="[param] enable: false" time="2026-04-17T07:15:01Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-17T07:15:01Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-17T07:15:01Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-17T07:15:01Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-17T07:15:02Z" level=info msg="Cache proxy is disabled in param or in backend" time="2026-04-17T07:15:02Z" level=info msg="[result] HTTP PROXY: " time="2026-04-17T07:15:02Z" level=info msg="[result] NO PROXY: " New PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn found after retrigger for component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn found for Component build-e2e-mofg/fj-multi-component-parent-flrm PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Running PipelineRun fj-multi-component-parent-flrm-on-pull-request-pknqn reason: Failed attempt 3/3: PipelineRun "fj-multi-component-parent-flrm-on-pull-request-pknqn" failed: pod: fj-multi-component-parent-flrm-on-pull-request-pknqn-init-pod | init container: prepare 2026/04/17 07:45:47 Entrypoint initialization pod: fj-multi-component-parent-flrm-on-pull-request-pknqn-init-pod | container step-init: time="2026-04-17T07:46:25Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-17T07:46:25Z" level=info msg="[param] enable: false" time="2026-04-17T07:46:25Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-17T07:46:25Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-17T07:46:25Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-17T07:46:25Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-17T07:46:26Z" level=info msg="Cache proxy is disabled in param or in backend" time="2026-04-17T07:46:26Z" level=info msg="[result] HTTP PROXY: " time="2026-04-17T07:46:26Z" level=info msg="[result] NO PROXY: " [FAILED] in [It] - /tmp/tmp.yHGHPgvWPm/tests/build/renovate.go:276 @ 04/17/26 08:02:42.52 << Timeline [FAILED] Expected success, but got an error: <*errors.errorString | 0xc0017b32c0>: pod: fj-multi-component-parent-flrm-on-pull-request-pknqn-init-pod | init container: prepare 2026/04/17 07:45:47 Entrypoint initialization pod: fj-multi-component-parent-flrm-on-pull-request-pknqn-init-pod | container step-init: time="2026-04-17T07:46:25Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-17T07:46:25Z" level=info msg="[param] enable: false" time="2026-04-17T07:46:25Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-17T07:46:25Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-17T07:46:25Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-17T07:46:25Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-17T07:46:26Z" level=info msg="Cache proxy is disabled in param or in backend" time="2026-04-17T07:46:26Z" level=info msg="[result] HTTP PROXY: " time="2026-04-17T07:46:26Z" level=info msg="[result] NO PROXY: " { s: "\n pod: fj-multi-component-parent-flrm-on-pull-request-pknqn-init-pod | init container: prepare\n2026/04/17 07:45:47 Entrypoint initialization\n\npod: fj-multi-component-parent-flrm-on-pull-request-pknqn-init-pod | container step-init: \ntime=\"2026-04-17T07:46:25Z\" level=info msg=\"Using in-cluster config\" logger=KubeClient\ntime=\"2026-04-17T07:46:25Z\" level=info msg=\"[param] enable: false\"\ntime=\"2026-04-17T07:46:25Z\" level=info msg=\"[param] default-http-proxy: squid.caching.svc.cluster.local:3128\"\ntime=\"2026-04-17T07:46:25Z\" level=info msg=\"[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai\"\ntime=\"2026-04-17T07:46:25Z\" level=info msg=\"[param] http-proxy-result-path: /tekton/results/http-proxy\"\ntime=\"2026-04-17T07:46:25Z\" level=info msg=\"[param] no-proxy-result-path: /tekton/results/no-proxy\"\ntime=\"2026-04-17T07:46:26Z\" level=info msg=\"Cache proxy is disabled in param or in backend\"\ntime=\"2026-04-17T07:46:26Z\" level=info msg=\"[result] HTTP PROXY: \"\ntime=\"2026-04-17T07:46:26Z\" level=info msg=\"[result] NO PROXY: \"\n", } In [It] at: /tmp/tmp.yHGHPgvWPm/tests/build/renovate.go:276 @ 04/17/26 08:02:42.52 ------------------------------ SSSSSSSSSSS••• ------------------------------ • [FAILED] [4013.594 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created [It] the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:366 Timeline >> PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn found for Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: PipelineRunStopping PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-2klxn reason: Failed attempt 1/3: PipelineRun "gl-test-custom-branch-kipmzi-on-pull-request-2klxn" failed: pod: gl-test-custom-branch-kipmzi-on-pull-request-2klxn-init-pod | init container: prepare 2026/04/17 07:10:18 Entrypoint initialization pod: gl-test-custom-branch-kipmzi-on-pull-request-2klxn-init-pod | container step-init: time="2026-04-17T07:10:28Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-17T07:10:28Z" level=info msg="[param] enable: false" time="2026-04-17T07:10:28Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-17T07:10:28Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-17T07:10:28Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-17T07:10:28Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-17T07:10:28Z" level=info msg="Cache proxy is disabled in param or in backend" time="2026-04-17T07:10:28Z" level=info msg="[result] HTTP PROXY: " time="2026-04-17T07:10:28Z" level=info msg="[result] NO PROXY: " New PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m found after retrigger for component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m found for Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-r965m reason: Failed attempt 2/3: PipelineRun "gl-test-custom-branch-kipmzi-on-pull-request-r965m" failed: pod: gl-test-custom-branch-kipmzi-on-pull-request-r965m-init-pod | init container: prepare 2026/04/17 07:34:56 Entrypoint initialization pod: gl-test-custom-branch-kipmzi-on-pull-request-r965m-init-pod | container step-init: time="2026-04-17T07:35:17Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-17T07:35:17Z" level=info msg="[param] enable: false" time="2026-04-17T07:35:17Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-17T07:35:17Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-17T07:35:17Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-17T07:35:17Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-17T07:35:20Z" level=info msg="Cache proxy is disabled in param or in backend" time="2026-04-17T07:35:20Z" level=info msg="[result] HTTP PROXY: " time="2026-04-17T07:35:20Z" level=info msg="[result] NO PROXY: " New PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q found after retrigger for component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q found for Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun has not been created yet for the Component build-e2e-spfj/gl-test-custom-branch-kipmzi PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Running PipelineRun gl-test-custom-branch-kipmzi-on-pull-request-cvz6q reason: Failed attempt 3/3: PipelineRun "gl-test-custom-branch-kipmzi-on-pull-request-cvz6q" failed: pod: gl-test-custom-branch-kipmzi-on-pull-request-cvz6q-init-pod | init container: prepare 2026/04/17 08:03:09 Entrypoint initialization pod: gl-test-custom-branch-kipmzi-on-pull-request-cvz6q-init-pod | container step-init: time="2026-04-17T08:03:15Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-17T08:03:15Z" level=info msg="[param] enable: false" time="2026-04-17T08:03:15Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-17T08:03:15Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-17T08:03:15Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-17T08:03:15Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-17T08:03:15Z" level=info msg="Cache proxy is disabled in param or in backend" time="2026-04-17T08:03:15Z" level=info msg="[result] HTTP PROXY: " time="2026-04-17T08:03:15Z" level=info msg="[result] NO PROXY: " [FAILED] in [It] - /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:368 @ 04/17/26 08:14:52.281 << Timeline [FAILED] Expected success, but got an error: <*errors.errorString | 0xc001a88240>: pod: gl-test-custom-branch-kipmzi-on-pull-request-cvz6q-init-pod | init container: prepare 2026/04/17 08:03:09 Entrypoint initialization pod: gl-test-custom-branch-kipmzi-on-pull-request-cvz6q-init-pod | container step-init: time="2026-04-17T08:03:15Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-17T08:03:15Z" level=info msg="[param] enable: false" time="2026-04-17T08:03:15Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-17T08:03:15Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-17T08:03:15Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-17T08:03:15Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-17T08:03:15Z" level=info msg="Cache proxy is disabled in param or in backend" time="2026-04-17T08:03:15Z" level=info msg="[result] HTTP PROXY: " time="2026-04-17T08:03:15Z" level=info msg="[result] NO PROXY: " { s: "\n pod: gl-test-custom-branch-kipmzi-on-pull-request-cvz6q-init-pod | init container: prepare\n2026/04/17 08:03:09 Entrypoint initialization\n\npod: gl-test-custom-branch-kipmzi-on-pull-request-cvz6q-init-pod | container step-init: \ntime=\"2026-04-17T08:03:15Z\" level=info msg=\"Using in-cluster config\" logger=KubeClient\ntime=\"2026-04-17T08:03:15Z\" level=info msg=\"[param] enable: false\"\ntime=\"2026-04-17T08:03:15Z\" level=info msg=\"[param] default-http-proxy: squid.caching.svc.cluster.local:3128\"\ntime=\"2026-04-17T08:03:15Z\" level=info msg=\"[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai\"\ntime=\"2026-04-17T08:03:15Z\" level=info msg=\"[param] http-proxy-result-path: /tekton/results/http-proxy\"\ntime=\"2026-04-17T08:03:15Z\" level=info msg=\"[param] no-proxy-result-path: /tekton/results/no-proxy\"\ntime=\"2026-04-17T08:03:15Z\" level=info msg=\"Cache proxy is disabled in param or in backend\"\ntime=\"2026-04-17T08:03:15Z\" level=info msg=\"[result] HTTP PROXY: \"\ntime=\"2026-04-17T08:03:15Z\" level=info msg=\"[result] NO PROXY: \"\n", } In [It] at: /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:368 @ 04/17/26 08:14:52.281 ------------------------------ SSSSSSSSSSSSSSS ------------------------------ P [PENDING] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged retrigger the pipeline manually [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:614 ------------------------------ P [PENDING] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged retriggered pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:656 ------------------------------ S•• ------------------------------ • [FAILED] [4105.096 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created [It] the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:366 Timeline >> PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 found for Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: PipelineRunStopping PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-w7w42 reason: Failed attempt 1/3: PipelineRun "gh-test-custom-branch-vdxmyv-on-pull-request-w7w42" failed: pod: gh-test-custom-branch-vdxmyv-on-pull-request-w7w42-init-pod | init container: prepare 2026/04/17 07:09:39 Entrypoint initialization pod: gh-test-custom-branch-vdxmyv-on-pull-request-w7w42-init-pod | container step-init: time="2026-04-17T07:09:41Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-17T07:09:41Z" level=info msg="[param] enable: false" time="2026-04-17T07:09:41Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-17T07:09:41Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-17T07:09:41Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-17T07:09:41Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-17T07:09:41Z" level=info msg="Cache proxy is disabled in param or in backend" time="2026-04-17T07:09:41Z" level=info msg="[result] HTTP PROXY: " time="2026-04-17T07:09:41Z" level=info msg="[result] NO PROXY: " New PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 found after retrigger for component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 found for Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-kn874 reason: Failed attempt 2/3: PipelineRun "gh-test-custom-branch-vdxmyv-on-pull-request-kn874" failed: pod: gh-test-custom-branch-vdxmyv-on-pull-request-kn874-init-pod | init container: prepare 2026/04/17 07:34:28 Entrypoint initialization pod: gh-test-custom-branch-vdxmyv-on-pull-request-kn874-init-pod | container step-init: time="2026-04-17T07:34:33Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-17T07:34:33Z" level=info msg="[param] enable: false" time="2026-04-17T07:34:33Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-17T07:34:33Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-17T07:34:33Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-17T07:34:33Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-17T07:34:33Z" level=info msg="Cache proxy is disabled in param or in backend" time="2026-04-17T07:34:33Z" level=info msg="[result] HTTP PROXY: " time="2026-04-17T07:34:33Z" level=info msg="[result] NO PROXY: " New PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 found after retrigger for component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 found for Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun has not been created yet for the Component build-e2e-omzc/gh-test-custom-branch-vdxmyv PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Running PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: PipelineRunStopping PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: PipelineRunStopping PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: PipelineRunStopping PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: PipelineRunStopping PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: PipelineRunStopping PipelineRun gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6 reason: Failed attempt 3/3: PipelineRun "gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6" failed: pod: gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6-init-pod | init container: prepare 2026/04/17 08:03:42 Entrypoint initialization pod: gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6-init-pod | container step-init: time="2026-04-17T08:04:23Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-17T08:04:23Z" level=info msg="[param] enable: false" time="2026-04-17T08:04:23Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-17T08:04:23Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-17T08:04:23Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-17T08:04:23Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-17T08:04:23Z" level=info msg="Cache proxy is disabled in param or in backend" time="2026-04-17T08:04:23Z" level=info msg="[result] HTTP PROXY: " time="2026-04-17T08:04:23Z" level=info msg="[result] NO PROXY: " [FAILED] in [It] - /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:368 @ 04/17/26 08:16:17.868 << Timeline [FAILED] Expected success, but got an error: <*errors.errorString | 0xc001688c30>: pod: gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6-init-pod | init container: prepare 2026/04/17 08:03:42 Entrypoint initialization pod: gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6-init-pod | container step-init: time="2026-04-17T08:04:23Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-17T08:04:23Z" level=info msg="[param] enable: false" time="2026-04-17T08:04:23Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-17T08:04:23Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-17T08:04:23Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-17T08:04:23Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-17T08:04:23Z" level=info msg="Cache proxy is disabled in param or in backend" time="2026-04-17T08:04:23Z" level=info msg="[result] HTTP PROXY: " time="2026-04-17T08:04:23Z" level=info msg="[result] NO PROXY: " { s: "\n pod: gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6-init-pod | init container: prepare\n2026/04/17 08:03:42 Entrypoint initialization\n\npod: gh-test-custom-branch-vdxmyv-on-pull-request-g7bx6-init-pod | container step-init: \ntime=\"2026-04-17T08:04:23Z\" level=info msg=\"Using in-cluster config\" logger=KubeClient\ntime=\"2026-04-17T08:04:23Z\" level=info msg=\"[param] enable: false\"\ntime=\"2026-04-17T08:04:23Z\" level=info msg=\"[param] default-http-proxy: squid.caching.svc.cluster.local:3128\"\ntime=\"2026-04-17T08:04:23Z\" level=info msg=\"[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai\"\ntime=\"2026-04-17T08:04:23Z\" level=info msg=\"[param] http-proxy-result-path: /tekton/results/http-proxy\"\ntime=\"2026-04-17T08:04:23Z\" level=info msg=\"[param] no-proxy-result-path: /tekton/results/no-proxy\"\ntime=\"2026-04-17T08:04:23Z\" level=info msg=\"Cache proxy is disabled in param or in backend\"\ntime=\"2026-04-17T08:04:23Z\" level=info msg=\"[result] HTTP PROXY: \"\ntime=\"2026-04-17T08:04:23Z\" level=info msg=\"[result] NO PROXY: \"\n", } In [It] at: /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:368 @ 04/17/26 08:16:17.868 ------------------------------ SSSSSSSSSSSSSSS ------------------------------ P [PENDING] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged retrigger the pipeline manually [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:614 ------------------------------ P [PENDING] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged retriggered pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:656 ------------------------------ S•••••••• ------------------------------ P [PENDING] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged retrigger the pipeline manually [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:614 ------------------------------ P [PENDING] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged retriggered pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:656 ------------------------------ • [FAILED] [22.941 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the component is removed and recreated (with the same name in the same namespace) [It] should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:729 Timeline >> Image repository for component fj-test-custom-branch-tbfysj in namespace build-e2e-aijk do not have right state ('' != 'ready') yet but it has status { { } { } []}. [FAILED] in [It] - /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:746 @ 04/17/26 08:20:59.398 Found purge PR with id: 4 << Timeline [FAILED] Failed after 5.480s. Unexpected error: <*errors.errorString | 0xc00168c480>: did not expect a new PR created in konflux-qe/devfile-sample-hello-world-vkkdpw repository after initial PaC configuration was already merged for the same component name and a namespace { s: "did not expect a new PR created in konflux-qe/devfile-sample-hello-world-vkkdpw repository after initial PaC configuration was already merged for the same component name and a namespace", } occurred In [It] at: /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:746 @ 04/17/26 08:20:59.398 ------------------------------ SSSSSSSSSSSSSSSSSSS Summarizing 6 Failures: [FAIL] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace [It] the PipelineRun should eventually finish successfully for parent component [build-service, renovate, multi-component, gitlab] /tmp/tmp.yHGHPgvWPm/tests/build/renovate.go:276 [FAIL] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace [It] PR merge triggers PAC PipelineRun for parent component [build-service, renovate, multi-component, github] /tmp/tmp.yHGHPgvWPm/tests/build/renovate.go:398 [FAIL] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] the PipelineRun should eventually finish successfully for parent component [build-service, renovate, multi-component, forgejo] /tmp/tmp.yHGHPgvWPm/tests/build/renovate.go:276 [FAIL] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created [It] the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:368 [FAIL] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created [It] the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:368 [FAIL] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the component is removed and recreated (with the same name in the same namespace) [It] should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /tmp/tmp.yHGHPgvWPm/tests/build/pac_build.go:746 Ran 92 of 464 Specs in 4548.654 seconds FAIL! -- 86 Passed | 6 Failed | 88 Pending | 284 Skipped Ginkgo ran 1 suite in 1h18m9.412974298s Test Suite Failed E0417 08:21:00.847260 18018 types.go:186] Failed to execute rule: build-service repo CI Workflow Rule: Execute the full workflow for e2e-tests repo in CI Error: running "ginkgo --seed=1776409365 --timeout=1h30m0s --grace-period=30s --output-interceptor-mode=none --label-filter=build-service --no-color --json-report=e2e-report.json --junit-report=e2e-report.xml --procs=20 --nodes=20 --p --output-dir=/workspace/artifact-dir ./cmd --" failed with exit code 1 make: *** [Makefile:25: ci/test/e2e] Error 1