WARNING: Using insecure TLS client config. Setting this option is not supported! Login successful. You have access to 75 projects, the list has been suppressed. You can list all projects with 'oc projects' Using project "default". Running gauge specs gauge run specs/pipelines/ log-level : [debug] tags : [sanity & !tls] verbose : [true] env will be loaded from default directory 'env' 'gauge_environment' set to 'default' Created gauge_screenshots_dir at /tmp/release-tests/.gauge/screenshots Compatible version of plugin go not found. Installing plugin go... Gathering metadata for go Downloading https://downloads.gauge.org/plugin/go?l=go&p=&o=linux&a=amd64 Downloading https://github.com/getgauge-contrib/gauge-go/releases/download/v0.4.0/gauge-go-0.4.0-linux.x86_64.zip ........................ Running plugin hook command => [go install github.com/go-delve/delve/cmd/dlv@latest] go: downloading github.com/go-delve/delve v1.25.1 go: downloading github.com/spf13/cobra v1.9.1 go: downloading golang.org/x/telemetry v0.0.0-20241106142447-58a1122356f5 go: downloading github.com/mattn/go-isatty v0.0.20 go: downloading github.com/spf13/pflag v1.0.6 go: downloading github.com/cosiner/argv v0.1.0 go: downloading github.com/derekparker/trie v0.0.0-20230829180723-39f4de51ef7d go: downloading github.com/go-delve/liner v1.2.3-0.20231231155935-4726ab1d7f62 go: downloading github.com/hashicorp/golang-lru v1.0.2 go: downloading golang.org/x/arch v0.11.0 go: downloading gopkg.in/yaml.v3 v3.0.1 go: downloading github.com/google/go-dap v0.12.0 go: downloading go.starlark.net v0.0.0-20231101134539-556fd59b42f6 go: downloading github.com/cilium/ebpf v0.11.0 go: downloading golang.org/x/sys v0.26.0 go: downloading github.com/mattn/go-runewidth v0.0.13 go: downloading github.com/cpuguy83/go-md2man/v2 v2.0.6 go: downloading golang.org/x/sync v0.8.0 go: downloading github.com/rivo/uniseg v0.2.0 go: downloading github.com/russross/blackfriday/v2 v2.1.0 go: downloading golang.org/x/exp v0.0.0-20230224173230-c95f2b4c22f2 Running plugin hook command => [go install github.com/getgauge-contrib/gauge-go@latest] go: downloading github.com/getgauge-contrib/gauge-go v0.5.0 go: downloading github.com/getgauge/common v0.0.0-20250512071011-6a075badb588 go: downloading google.golang.org/protobuf v1.36.6 go: downloading github.com/golang/protobuf v1.5.4 go: downloading github.com/dmotylev/goproperties v0.0.0-20140630191356-7cbffbaada47 Installing plugin go 0.4.0 Successfully installed plugin 'go' version 0.4.0 Compatible version of plugin html-report not found. Installing plugin html-report... Gathering metadata for html-report Downloading https://downloads.gauge.org/plugin/html-report?l=go&p=go&o=linux&a=amd64 Downloading https://github.com/getgauge/html-report/releases/download/v4.3.3/html-report-4.3.3-linux.x86_64.zip ........................ Installing plugin html-report 4.3.3 Successfully installed plugin 'html-report' version 4.3.3 Compatible version of plugin xml-report not found. Installing plugin xml-report... Gathering metadata for xml-report Downloading https://downloads.gauge.org/plugin/xml-report?l=go&p=go,html-report&o=linux&a=amd64 Downloading https://github.com/getgauge/xml-report/releases/download/v0.5.2/xml-report-0.5.2-linux.x86_64.zip ....................... Installing plugin xml-report 0.5.2 Successfully installed plugin 'xml-report' version 0.5.2 Parsing started. Started concepts parsing. 14 concepts parsing completed. Started specifications parsing. 7 specifications parsing completed. Applying tags filter: sanity & !tls The following specifications satisfy filter criteria: specs/pipelines/bundles-resolver.spec specs/pipelines/cluster-resolvers.spec specs/pipelines/fail.spec specs/pipelines/git-resolvers.spec specs/pipelines/http-resolvers.spec specs/pipelines/hub-resolvers.spec specs/pipelines/run.spec Parsing completed. Starting go runner go: downloading k8s.io/apimachinery v0.32.4 go: downloading github.com/getgauge-contrib/gauge-go v0.4.0 go: downloading github.com/openshift/api v0.0.0-20240521185306-0314f31e7774 go: downloading gotest.tools/v3 v3.5.2 go: downloading github.com/openshift/client-go v0.0.0-20240523113335-452272e0496d go: downloading github.com/tektoncd/pipeline v1.0.0 go: downloading k8s.io/api v0.32.4 go: downloading github.com/openshift-pipelines/manual-approval-gate v0.6.0 go: downloading github.com/openshift-pipelines/pipelines-as-code v0.35.0 go: downloading go.opencensus.io v0.24.0 go: downloading github.com/operator-framework/api v0.16.0 go: downloading github.com/tektoncd/operator v0.76.0 Checking updates... Downloading https://downloads.gauge.org/plugin/go?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Downloading https://downloads.gauge.org/plugin/html-report?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Downloading https://downloads.gauge.org/plugin/xml-report?l=go&p=go,html-report,xml-report&o=linux&a=amd64 go: downloading github.com/pkg/errors v0.9.1 go: downloading github.com/prometheus/client_golang v1.22.0 go: downloading github.com/tektoncd/cli v0.41.0 go: downloading knative.dev/pkg v0.0.0-20250424013628-d5e74d29daa3 go: downloading github.com/prometheus/common v0.63.0 go: downloading github.com/operator-framework/operator-lifecycle-manager v0.22.0 go: downloading k8s.io/client-go v0.32.4 go: downloading github.com/xanzy/go-gitlab v0.109.0 go: downloading github.com/tektoncd/triggers v0.32.0 go: downloading github.com/google/go-cmp v0.7.0 go: downloading gopkg.in/yaml.v2 v2.4.0 go: downloading github.com/getgauge/common v0.0.0-20211105093448-e0aee1ccb217 go: downloading github.com/golang/groupcache v0.0.0-20241129210726-2c02b8208cf8 go: downloading github.com/sirupsen/logrus v1.9.3 go: downloading github.com/gogo/protobuf v1.3.2 go: downloading github.com/google/gofuzz v1.2.0 go: downloading k8s.io/utils v0.0.0-20250502105355-0f33e8f1c979 go: downloading k8s.io/klog/v2 v2.130.1 go: downloading github.com/fatih/color v1.18.0 go: downloading github.com/jonboulle/clockwork v0.5.0 go: downloading github.com/json-iterator/go v1.1.12 go: downloading go.uber.org/multierr v1.11.0 go: downloading k8s.io/cli-runtime v0.29.15 go: downloading sigs.k8s.io/yaml v1.4.0 go: downloading github.com/manifestival/manifestival v0.7.2 go: downloading go.uber.org/zap v1.27.0 go: downloading github.com/prometheus/client_model v0.6.2 go: downloading github.com/AlecAivazis/survey/v2 v2.3.7 go: downloading github.com/ktr0731/go-fuzzyfinder v0.8.0 go: downloading github.com/google/cel-go v0.25.0 go: downloading k8s.io/kube-openapi v0.0.0-20231010175941-2dd684a91f00 go: downloading sigs.k8s.io/structured-merge-diff/v4 v4.7.0 go: downloading github.com/google/go-querystring v1.1.0 go: downloading github.com/hashicorp/go-cleanhttp v0.5.2 go: downloading github.com/hashicorp/go-retryablehttp v0.7.7 go: downloading golang.org/x/oauth2 v0.30.0 go: downloading golang.org/x/time v0.11.0 go: downloading github.com/davecgh/go-spew v1.1.2-0.20180830191138-d8f796af33cc go: downloading github.com/mattn/go-colorable v0.1.14 go: downloading github.com/mgutz/ansi v0.0.0-20200706080929-d51e80ef957d go: downloading golang.org/x/text v0.24.0 go: downloading github.com/blang/semver/v4 v4.0.0 go: downloading golang.org/x/sys v0.33.0 go: downloading gopkg.in/inf.v0 v0.9.1 go: downloading sigs.k8s.io/json v0.0.0-20241014173422-cfa47c3a1cc8 go: downloading github.com/go-logr/logr v1.4.2 go: downloading golang.org/x/term v0.32.0 go: downloading github.com/hako/durafmt v0.0.0-20210608085754-5c1018a4e16b go: downloading github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd go: downloading github.com/modern-go/reflect2 v1.0.2 go: downloading github.com/evanphx/json-patch/v5 v5.9.11 go: downloading github.com/openshift/apiserver-library-go v0.0.0-20230816171015-6bfafa975bfb go: downloading golang.org/x/xerrors v0.0.0-20240903120638-7835f813f4da go: downloading knative.dev/eventing v0.45.0 go: downloading github.com/evanphx/json-patch v5.9.0+incompatible go: downloading github.com/blendle/zapdriver v1.3.1 go: downloading github.com/cloudevents/sdk-go/v2 v2.16.0 go: downloading github.com/tidwall/sjson v1.2.5 go: downloading github.com/google/uuid v1.6.0 go: downloading golang.org/x/sync v0.14.0 go: downloading golang.org/x/net v0.39.0 go: downloading github.com/kballard/go-shellquote v0.0.0-20180428030007-95032a82bc51 go: downloading github.com/google/gnostic-models v0.6.9 go: downloading github.com/munnerz/goautoneg v0.0.0-20191010083416-a7dc8b61c822 go: downloading github.com/gdamore/tcell/v2 v2.6.0 go: downloading github.com/ktr0731/go-ansisgr v0.1.0 go: downloading github.com/mattn/go-runewidth v0.0.16 go: downloading github.com/nsf/termbox-go v1.1.1 go: downloading github.com/fxamacker/cbor/v2 v2.8.0 go: downloading github.com/liggitt/tabwriter v0.0.0-20181228230101-89fcab3d43de go: downloading github.com/moby/term v0.5.2 go: downloading contrib.go.opencensus.io/exporter/prometheus v0.4.2 go: downloading contrib.go.opencensus.io/exporter/ocagent v0.7.1-0.20200907061046-05415f1de66d go: downloading google.golang.org/grpc v1.72.0 go: downloading k8s.io/apiextensions-apiserver v0.32.4 go: downloading gomodules.xyz/jsonpatch/v2 v2.5.0 go: downloading cel.dev/expr v0.23.1 go: downloading google.golang.org/genproto/googleapis/api v0.0.0-20250428153025-10db94c68c34 go: downloading github.com/kelseyhightower/envconfig v1.4.0 go: downloading sigs.k8s.io/kustomize/api v0.13.5-0.20230601165947-6ce0bf390ce3 go: downloading sigs.k8s.io/kustomize/kyaml v0.14.3-0.20230601165947-6ce0bf390ce3 go: downloading github.com/gregjones/httpcache v0.0.0-20190611155906-901d90724c79 go: downloading github.com/peterbourgon/diskv v2.0.1+incompatible go: downloading github.com/hashicorp/go-multierror v1.1.1 go: downloading github.com/tidwall/gjson v1.14.2 go: downloading gopkg.in/evanphx/json-patch.v4 v4.12.0 go: downloading sigs.k8s.io/controller-runtime v0.15.3 go: downloading github.com/go-openapi/jsonreference v0.21.0 go: downloading github.com/go-openapi/swag v0.23.1 go: downloading github.com/emicklei/go-restful/v3 v3.12.2 go: downloading github.com/rivo/uniseg v0.4.7 go: downloading github.com/gdamore/encoding v1.0.0 go: downloading github.com/lucasb-eyer/go-colorful v1.2.0 go: downloading github.com/x448/float16 v0.8.4 go: downloading github.com/stoewer/go-strcase v1.3.0 go: downloading github.com/antlr4-go/antlr/v4 v4.13.1 go: downloading github.com/prometheus/statsd_exporter v0.28.0 go: downloading github.com/census-instrumentation/opencensus-proto v0.4.1 go: downloading google.golang.org/api v0.231.0 go: downloading google.golang.org/genproto/googleapis/rpc v0.0.0-20250428153025-10db94c68c34 go: downloading github.com/google/btree v1.1.3 go: downloading github.com/hashicorp/errwrap v1.1.0 go: downloading github.com/tidwall/match v1.1.1 go: downloading github.com/tidwall/pretty v1.2.0 go: downloading github.com/go-openapi/jsonpointer v0.21.1 go: downloading github.com/mailru/easyjson v0.9.0 go: downloading github.com/beorn7/perks v1.0.1 go: downloading github.com/cespare/xxhash/v2 v2.3.0 go: downloading github.com/prometheus/procfs v0.16.1 go: downloading golang.org/x/exp v0.0.0-20250408133849-7e4ce0ab07d0 go: downloading github.com/grpc-ecosystem/grpc-gateway/v2 v2.26.3 go: downloading github.com/imdario/mergo v0.3.16 go: downloading github.com/go-errors/errors v1.4.2 go: downloading github.com/josharian/intern v1.0.0 go: downloading github.com/monochromegane/go-gitignore v0.0.0-20200626010858-205db1a8cc00 go: downloading github.com/xlab/treeprint v1.2.0 go: downloading github.com/google/shlex v0.0.0-20191202100458-e7afc7fbc510 go: downloading go.starlark.net v0.0.0-20230525235612-a134d8f9ddca Established connection to runner. Validation started. Validation completed. Run started Starting Html Report plugin Setting MaxRecvMsgSize = 1024 MB Attempting to connect to grpc server at port: 36545 Successfully made the connection with plugin with port: 36545 Starting Xml Report plugin Attempting to connect to grpc server at port: 41117 Successfully made the connection with plugin with port: 41117 Initialising suite data store. # Bundles resolver spec  ## Test the functionality of bundles resolver with parameter: PIPELINES-25-TC02 2025/08/04 16:00:40 output: Now using project "releasetest-d2j2r" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname 2025/08/04 16:00:46 Waiting for operator to be up and running.... 2025/08/04 16:00:46 Operator is up  * Validate Operator should be installed ...[PASS] 2025/08/04 16:00:46 output: pipelinerun.tekton.dev/bundles-resolver-pipelinerun-param created  * Create |S.NO|resource_dir | |----|-----------------------------------------------------------------------| |1 |testdata/resolvers/pipelineruns/bundles-resolver-pipelinerun-param.yaml| ...[PASS] 2025/08/04 16:00:46 validating pipeline run bundles-resolver-pipelinerun-param for success state... 2025/08/04 16:01:11 pipelineRun: bundles-resolver-pipelinerun-param is successful under namespace : releasetest-d2j2r  * Verify pipelinerun |S.NO|pipeline_run_name |status | |----|----------------------------------|----------| |1 |bundles-resolver-pipelinerun-param|successful| ...[PASS] 2025/08/04 16:02:41 output: project.project.openshift.io "releasetest-d2j2r" deleted # Cluster resolvers spec  ## Checking the functionality of cluster resolvers#1: PIPELINES-23-TC01 2025/08/04 16:02:41 output: Now using project "releasetest-vx9sc" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname 2025/08/04 16:02:46 Check if project releasetest-tasks already exists 2025/08/04 16:02:46 Creating project releasetest-tasks 2025/08/04 16:02:46 output: Now using project "releasetest-tasks" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Create project "releasetest-tasks" ...[PASS] 2025/08/04 16:02:46 output: task.tekton.dev/resolver-task created 2025/08/04 16:02:46 output: task.tekton.dev/resolver-task2 created  * Apply |S.NO|resource_dir | |----|--------------------------------------------| |1 |testdata/resolvers/tasks/resolver-task.yaml | |2 |testdata/resolvers/tasks/resolver-task2.yaml| ...[PASS] 2025/08/04 16:02:46 Check if project releasetest-pipelines already exists 2025/08/04 16:02:47 Creating project releasetest-pipelines 2025/08/04 16:02:47 output: Now using project "releasetest-pipelines" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Create project "releasetest-pipelines" ...[PASS] 2025/08/04 16:02:47 output: pipeline.tekton.dev/resolver-pipeline created  * Apply |S.NO|resource_dir | |----|---------------------------------------------------| |1 |testdata/resolvers/pipelines/resolver-pipeline.yaml| ...[PASS] 2025/08/04 16:02:47 Switch to project releasetest-vx9sc  * Switch to autogenerated namespace ...[PASS] 2025/08/04 16:02:47 output: pipelinerun.tekton.dev/resolver-pipelinerun created  * Create |S.NO|resource_dir | |----|---------------------------------------------------------| |1 |testdata/resolvers/pipelineruns/resolver-pipelinerun.yaml| ...[PASS] 2025/08/04 16:02:47 validating pipeline run resolver-pipelinerun for success state... 2025/08/04 16:02:57 pipelineRun: resolver-pipelinerun is successful under namespace : releasetest-vx9sc  * Verify pipelinerun |S.NO|pipeline_run_name |status | |----|--------------------|----------| |1 |resolver-pipelinerun|successful| ...[PASS] 2025/08/04 16:04:27 output: project.project.openshift.io "releasetest-vx9sc" deleted # Verify Pipeline Failures  ## Run Pipeline with a non-existent ServiceAccount: PIPELINES-02-TC01 2025/08/04 16:04:27 output: Now using project "releasetest-h6kcr" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:04:32 Verify SA "foobar" is absent in namespace "releasetest-h6kcr"  * Verify ServiceAccount "foobar" does not exist ...[PASS] 2025/08/04 16:04:33 output: task.tekton.dev/create-file-vb created task.tekton.dev/check-stuff-file-exists-vb created pipeline.tekton.dev/output-pipeline-vb created pipelinerun.tekton.dev/output-pipeline-run-vb created  * Create |S.NO|resource_dir | |----|------------------------------------------| |1 |testdata/negative/v1beta1/pipelinerun.yaml| ...[PASS] 2025/08/04 16:04:33 validating pipeline run output-pipeline-run-vb for failure state... 2025/08/04 16:04:33 Waiting for PipelineRun in namespace releasetest-h6kcr to fail  * Verify pipelinerun |S.NO|pipeline_run_name |status | |----|----------------------|-------| |1 |output-pipeline-run-vb|Failure| ...[PASS] 2025/08/04 16:04:53 output: project.project.openshift.io "releasetest-h6kcr" deleted # Git resolvers spec  ## Test the functionality of git resolvers: PIPELINES-24-TC01 2025/08/04 16:04:53 output: Now using project "releasetest-lsfzz" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:04:58 output: pipelinerun.tekton.dev/git-resolver-pipelinerun created  * Create |S.NO|resource_dir | |----|-------------------------------------------------------------| |1 |testdata/resolvers/pipelineruns/git-resolver-pipelinerun.yaml| ...[PASS] 2025/08/04 16:04:58 validating pipeline run git-resolver-pipelinerun for success state... 2025/08/04 16:05:08 pipelineRun: git-resolver-pipelinerun is successful under namespace : releasetest-lsfzz  * Verify pipelinerun |S.NO|pipeline_run_name |status | |----|------------------------|----------| |1 |git-resolver-pipelinerun|successful| ...[PASS] 2025/08/04 16:06:38 output: project.project.openshift.io "releasetest-lsfzz" deleted # http resolvers spec  ## Test the functionality of http resolvers: PIPELINES-31-TC01 2025/08/04 16:06:38 output: Now using project "releasetest-6vkhp" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:06:43 output: pipelinerun.tekton.dev/http-resolver-pipelinerun created  * Create |S.NO|resource_dir | |----|--------------------------------------------------------------| |1 |testdata/resolvers/pipelineruns/http-resolver-pipelinerun.yaml| ...[PASS] 2025/08/04 16:06:43 validating pipeline run http-resolver-pipelinerun for success state... 2025/08/04 16:07:08 pipelineRun: http-resolver-pipelinerun is successful under namespace : releasetest-6vkhp  * Verify pipelinerun |S.NO|pipeline_run_name |status | |----|-------------------------|----------| |1 |http-resolver-pipelinerun|successful| ...[PASS] 2025/08/04 16:08:38 output: project.project.openshift.io "releasetest-6vkhp" deleted # HUB resolvers spec  ## Test the functionality of hub resolvers 2025/08/04 16:08:39 output: Now using project "releasetest-xr5jw" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:08:44 output: pipeline.tekton.dev/hub-git-cli-pipeline created 2025/08/04 16:08:44 output: persistentvolumeclaim/shared-pvc created 2025/08/04 16:08:44 output: pipelinerun.tekton.dev/hub-git-cli-run created  * Apply |S.NO|resource_dir | |----|------------------------------------------------| |1 |testdata/resolvers/pipelines/git-cli-hub.yaml | |2 |testdata/pvc/pvc.yaml | |3 |testdata/resolvers/pipelineruns/git-cli-hub.yaml| ...[PASS] 2025/08/04 16:08:44 validating pipeline run hub-git-cli-run for success state... 2025/08/04 16:09:14 pipelineRun: hub-git-cli-run is successful under namespace : releasetest-xr5jw  * Verify pipelinerun |S.NO|pipeline_run_name|status | |----|-----------------|----------| |1 |hub-git-cli-run |successful| ...[PASS] 2025/08/04 16:10:44 output: project.project.openshift.io "releasetest-xr5jw" deleted # Verify Pipeline E2E spec  ## Pipelinerun Timeout failure Test: PIPELINES-03-TC04 2025/08/04 16:10:44 output: Now using project "releasetest-c2k7x" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:10:50 output: task.tekton.dev/banana created pipeline.tekton.dev/tomatoes created pipelinerun.tekton.dev/pear created  * Create |S.NO|resource_dir | |----|----------------------------------------------------| |1 |testdata/v1beta1/pipelinerun/pipelineruntimeout.yaml| ...[PASS] 2025/08/04 16:10:50 validating pipeline run pear to time out... 2025/08/04 16:10:50 Waiting for Pipelinerun pear in namespace releasetest-c2k7x to be started 2025/08/04 16:10:55 Waiting for TaskRuns from PipelineRun pear in namespace releasetest-c2k7x to be running 2025/08/04 16:10:55 Waiting for PipelineRun pear in namespace releasetest-c2k7x to be timed out 2025/08/04 16:11:00 Waiting for TaskRuns from PipelineRun pear in namespace releasetest-c2k7x to be cancelled  * Verify pipelinerun |S.NO|pipeline_run_name|status | |----|-----------------|-------| |1 |pear |timeout| ...[PASS] 2025/08/04 16:12:30 output: project.project.openshift.io "releasetest-c2k7x" deleted  ## Configure execution results at the Task level Test: PIPELINES-03-TC05 2025/08/04 16:12:30 output: Now using project "releasetest-pbkbz" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:12:35 output: pipeline.tekton.dev/sum-and-multiply-pipeline created task.tekton.dev/sum created task.tekton.dev/multiply created pipelinerun.tekton.dev/task-level-results created  * Create |S.NO|resource_dir | |----|------------------------------------------------------| |1 |testdata/v1beta1/pipelinerun/task_results_example.yaml| ...[PASS] 2025/08/04 16:12:35 validating pipeline run task-level-results for success state... 2025/08/04 16:12:50 pipelineRun: task-level-results is successful under namespace : releasetest-pbkbz  * Verify pipelinerun |S.NO|pipeline_run_name |status | |----|------------------|----------| |1 |task-level-results|successful| ...[PASS] 2025/08/04 16:14:20 output: project.project.openshift.io "releasetest-pbkbz" deleted  ## Cancel pipelinerun Test: PIPELINES-03-TC06 2025/08/04 16:14:20 output: Now using project "releasetest-42pdw" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:14:25 output: persistentvolumeclaim/shared-pvc created 2025/08/04 16:14:26 output: task.tekton.dev/create-file-v1b1 created task.tekton.dev/check-file-exists-v1b1 created pipeline.tekton.dev/output-pipeline-v1b1 created pipelinerun.tekton.dev/output-pipeline-run-v1b1 created  * Create |S.NO|resource_dir | |----|---------------------------------------------| |1 |testdata/pvc/pvc.yaml | |2 |testdata/v1beta1/pipelinerun/pipelinerun.yaml| ...[PASS] 2025/08/04 16:14:26 validating pipeline run output-pipeline-run-v1b1 to be cancelled... 2025/08/04 16:14:26 Waiting for Pipelinerun output-pipeline-run-v1b1 in namespace releasetest-42pdw to be started 2025/08/04 16:14:31 Canceling pipeline run: PipelineRun cancelled: output-pipeline-run-v1b1 2025/08/04 16:14:36 Waiting for TaskRuns in PipelineRun output-pipeline-run-v1b1 in namespace releasetest-42pdw to be cancelled  * Verify pipelinerun |S.NO|pipeline_run_name |status | |----|------------------------|---------| |1 |output-pipeline-run-v1b1|cancelled| ...[PASS] 2025/08/04 16:16:06 output: project.project.openshift.io "releasetest-42pdw" deleted  ## Pipelinerun with large result: PIPELINES-03-TC08 2025/08/04 16:16:06 output: Now using project "releasetest-7747m" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:16:11 output: task.tekton.dev/print-result created task.tekton.dev/generate-result created pipeline.tekton.dev/result-test created pipelinerun.tekton.dev/result-test-run created  * Create |S.NO|resource_dir | |----|---------------------------------------------------------------| |1 |testdata/v1beta1/pipelinerun/pipelinerun-with-large-result.yaml| ...[PASS] 2025/08/04 16:16:11 validating pipeline run result-test-run for success state... 2025/08/04 16:16:21 pipelineRun: result-test-run is successful under namespace : releasetest-7747m  * Verify pipelinerun |S.NO|pipeline_run_name|status | |----|-----------------|----------| |1 |result-test-run |successful| ...[PASS] 2025/08/04 16:17:51 output: project.project.openshift.io "releasetest-7747m" deleted Successfully generated xml-report to => /logs/artifacts/xml-report/2025-08-04 16.17.51 Transformed SuiteResult to report structure Successfully generated html-report to => /logs/artifacts/html-report/2025-08-04_16.17.51/index.html Done generating HTML report using theme from /tmp/plugins/html-report/4.3.3/themes/default Sending kill message to Html Report plugin. Sending kill message to Xml Report plugin. Sending kill message to runner. ok command-line-arguments 1031.817s Runner with PID:3786 has exited Specifications: 7 executed 7 passed 0 failed 0 skipped Scenarios: 10 executed 10 passed 0 failed 0 skipped Total time taken: 17m11.369s Updates are available. Run `gauge update -c` for more info. gauge run specs/triggers/ log-level : [debug] tags : [sanity & !tls] verbose : [true] env will be loaded from default directory 'env' 'gauge_environment' set to 'default' Created gauge_screenshots_dir at /tmp/release-tests/.gauge/screenshots Plugin go is already installed. Plugin html-report is already installed. Plugin xml-report is already installed. Parsing started. Started concepts parsing. 14 concepts parsing completed. Started specifications parsing. 4 specifications parsing completed. Applying tags filter: sanity & !tls The following specifications satisfy filter criteria: specs/triggers/cron.spec specs/triggers/eventlistener.spec specs/triggers/triggerbinding.spec specs/triggers/tutorial.spec Parsing completed. Starting go runner Checking updates... Downloading https://downloads.gauge.org/plugin/go?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Downloading https://downloads.gauge.org/plugin/html-report?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Downloading https://downloads.gauge.org/plugin/xml-report?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Established connection to runner. Validation started. Validation completed. Run started Starting Html Report plugin Attempting to connect to grpc server at port: 36703 Successfully made the connection with plugin with port: 36703 Starting Xml Report plugin Attempting to connect to grpc server at port: 46029 Successfully made the connection with plugin with port: 46029 Initialising suite data store. # Verify Triggers with cronjob  ## Create Triggers using k8s cronJob: PIPELINES-04-TC01 2025/08/04 16:17:58 output: Now using project "releasetest-dww2j" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname 2025/08/04 16:18:03 Waiting for operator to be up and running.... 2025/08/04 16:18:03 Operator is up  * Validate Operator should be installed ...[PASS] 2025/08/04 16:18:03 output: task.tekton.dev/say-hello created task.tekton.dev/say-message created task.tekton.dev/say-bye created pipeline.tekton.dev/simple-pipeline created 2025/08/04 16:18:03 output: triggerbinding.triggers.tekton.dev/cron-binding created 2025/08/04 16:18:03 output: triggertemplate.triggers.tekton.dev/pipeline-template created 2025/08/04 16:18:03 output: eventlistener.triggers.tekton.dev/cron-listener created  * Create |S.NO|resource_dir | |----|--------------------------------------------| |1 |testdata/triggers/cron/example-pipeline.yaml| |2 |testdata/triggers/cron/triggerbinding.yaml | |3 |testdata/triggers/cron/triggertemplate.yaml | |4 |testdata/triggers/cron/eventlistener.yaml | ...[PASS] 2025/08/04 16:18:03 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:18:03 +0000 UTC} Reason: Message:Deployment exists} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:18:03 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:18:03 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000858cf0 Addresses:[]} Configuration:{GeneratedResourceName:el-cron-listener}} 2025/08/04 16:18:08 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:False Severity: LastTransitionTime:{Inner:2025-08-04 16:18:03 +0000 UTC} Reason:MinimumReplicasUnavailable Message:Deployment does not have minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:18:03 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:18:03 +0000 UTC} Reason:ReplicaSetUpdated Message:ReplicaSet "el-cron-listener-84b9d49b57" is progressing.} {Type:Ready Status:False Severity: LastTransitionTime:{Inner:2025-08-04 16:18:03 +0000 UTC} Reason: Message:Condition Available has status: False with message: Deployment does not have minimum availability.} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:18:03 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000928120 Addresses:[]} Configuration:{GeneratedResourceName:el-cron-listener}} 2025/08/04 16:18:13 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:18:08 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:18:08 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:18:08 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-cron-listener-84b9d49b57" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:18:08 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:18:08 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc0008dc270 Addresses:[]} Configuration:{GeneratedResourceName:el-cron-listener}} 2025/08/04 16:18:13 sinkpod name: el-cron-listener-84b9d49b57-d9c7x 2025/08/04 16:18:14 Route url: 'http://el-cron-listener-releasetest-dww2j.apps.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com'  * Expose Event listener "cron-listener" ...[PASS] 2025/08/04 16:18:19 Verify that image stream "golang" exists in namespace "openshift"  * Verify that image stream "golang" exists ...[PASS] 2025/08/04 16:18:19 Cronjob: hello created in namespace: releasetest-dww2j  * Create cron job with schedule "*/1 * * * *" ...[PASS] 2025/08/04 16:19:01 pipeline run : simple-pipeline-run-clwdk 2025/08/04 16:20:01 pipeline run : simple-pipeline-run-zgpxd 2025/08/04 16:21:01 pipeline run : simple-pipeline-run-2cktr 2025/08/04 16:22:01 pipeline run : simple-pipeline-run-n9f2j 2025/08/04 16:23:01 pipeline run : simple-pipeline-run-6qv8p  * Watch for pipelinerun resources ...[PASS]  * Delete cron job ...[PASS]  * Assert no new pipelineruns created ...[PASS] 2025/08/04 16:24:19 Deleted EventListener 2025/08/04 16:24:24 EventListener's Deployment was deleted 2025/08/04 16:24:24 EventListener's Service was deleted 2025/08/04 16:24:24 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2025/08/04 16:25:54 output: project.project.openshift.io "releasetest-dww2j" deleted # Verify eventlisteners spec  ## Create Eventlistener embedded TriggersBindings specs: PIPELINES-05-TC08 2025/08/04 16:25:54 output: Now using project "releasetest-27cht" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:25:59 output: task.tekton.dev/say-hello created task.tekton.dev/say-message created task.tekton.dev/say-bye created pipeline.tekton.dev/simple-pipeline created 2025/08/04 16:26:00 output: triggerbinding.triggers.tekton.dev/pipeline-binding created 2025/08/04 16:26:00 output: triggertemplate.triggers.tekton.dev/pipeline-template created 2025/08/04 16:26:00 output: eventlistener.triggers.tekton.dev/listener-embed-binding created  * Create |S.NO|resource_dir | |----|-------------------------------------------------------------------| |1 |testdata/triggers/sample-pipeline.yaml | |2 |testdata/triggers/triggerbindings/triggerbinding.yaml | |3 |testdata/triggers/triggertemplate/triggertemplate.yaml | |4 |testdata/triggers/eventlisteners/eventlistener-embeded-binding.yaml| ...[PASS] 2025/08/04 16:26:00 triggerbinding pipeline-binding exists  * Verify that "triggerbinding" "pipeline-binding" exists ...[PASS] 2025/08/04 16:26:00 triggertemplate pipeline-template exists  * Verify that "triggertemplate" "pipeline-template" exists ...[PASS] 2025/08/04 16:26:00 eventlistener listener-embed-binding exists  * Verify that "eventlistener" "listener-embed-binding" exists ...[PASS] 2025/08/04 16:26:00 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:False Severity: LastTransitionTime:{Inner:2025-08-04 16:26:00 +0000 UTC} Reason:MinimumReplicasUnavailable Message:Deployment does not have minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:26:00 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:26:00 +0000 UTC} Reason:ReplicaSetUpdated Message:ReplicaSet "el-listener-embed-binding-5fbf4598b" is progressing.} {Type:Ready Status:False Severity: LastTransitionTime:{Inner:2025-08-04 16:26:00 +0000 UTC} Reason: Message:Condition Available has status: False with message: Deployment does not have minimum availability.} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:26:00 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000aa4b10 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-embed-binding}} 2025/08/04 16:26:05 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:26:01 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:26:01 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:26:01 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-listener-embed-binding-5fbf4598b" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:26:01 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:26:01 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000999e60 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-embed-binding}} 2025/08/04 16:26:05 sinkpod name: el-listener-embed-binding-5fbf4598b-4dxdp 2025/08/04 16:26:06 Route url: 'http://el-listener-embed-binding-releasetest-27cht.apps.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com'  * Expose Event listener "listener-embed-binding" ...[PASS] 2025/08/04 16:26:11 Building headers for github interceptor..  * Mock post event to "github" interceptor with event-type "push", payload "testdata/push.json", with TLS "false" ...[PASS]  * Assert eventlistener response ...[PASS] 2025/08/04 16:26:11 validating pipeline run simple-pipeline-run for success state... 2025/08/04 16:26:26 pipelineRun: simple-pipeline-run is successful under namespace : releasetest-27cht  * Verify pipelinerun |S.NO|pipeline_run_name |status | |----|-------------------|----------| |1 |simple-pipeline-run|successful| ...[PASS] 2025/08/04 16:26:26 Deleted EventListener 2025/08/04 16:26:31 EventListener's Deployment was deleted 2025/08/04 16:26:31 EventListener's Service was deleted 2025/08/04 16:26:31 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2025/08/04 16:28:01 output: project.project.openshift.io "releasetest-27cht" deleted  ## Create embedded TriggersTemplate: PIPELINES-05-TC09 2025/08/04 16:28:01 output: Now using project "releasetest-czzgr" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:28:06 output: triggerbinding.triggers.tekton.dev/pipeline-binding created 2025/08/04 16:28:07 output: triggertemplate.triggers.tekton.dev/pipeline-template created 2025/08/04 16:28:07 output: eventlistener.triggers.tekton.dev/listener-embed-binding created  * Create |S.NO|resource_dir | |----|-------------------------------------------------------------------| |1 |testdata/triggers/triggerbindings/triggerbinding.yaml | |2 |testdata/triggers/triggertemplate/embed-triggertemplate.yaml | |3 |testdata/triggers/eventlisteners/eventlistener-embeded-binding.yaml| ...[PASS] 2025/08/04 16:28:07 triggerbinding pipeline-binding exists  * Verify that "triggerbinding" "pipeline-binding" exists ...[PASS] 2025/08/04 16:28:07 triggertemplate pipeline-template exists  * Verify that "triggertemplate" "pipeline-template" exists ...[PASS] 2025/08/04 16:28:07 eventlistener listener-embed-binding exists  * Verify that "eventlistener" "listener-embed-binding" exists ...[PASS] 2025/08/04 16:28:07 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:False Severity: LastTransitionTime:{Inner:2025-08-04 16:28:07 +0000 UTC} Reason:MinimumReplicasUnavailable Message:Deployment does not have minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:28:07 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:28:07 +0000 UTC} Reason:ReplicaSetUpdated Message:ReplicaSet "el-listener-embed-binding-7c58cbf458" is progressing.} {Type:Ready Status:False Severity: LastTransitionTime:{Inner:2025-08-04 16:28:07 +0000 UTC} Reason: Message:Condition Available has status: False with message: Deployment does not have minimum availability.} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:28:07 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000e8ca20 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-embed-binding}} 2025/08/04 16:28:12 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:28:09 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:28:09 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:28:09 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-listener-embed-binding-7c58cbf458" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:28:09 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:28:09 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000954bd0 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-embed-binding}} 2025/08/04 16:28:12 sinkpod name: el-listener-embed-binding-7c58cbf458-wq6n7 2025/08/04 16:28:13 Route url: 'http://el-listener-embed-binding-releasetest-czzgr.apps.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com'  * Expose Event listener "listener-embed-binding" ...[PASS] 2025/08/04 16:28:18 Building headers for github interceptor..  * Mock post event to "github" interceptor with event-type "push", payload "testdata/push.json", with TLS "false" ...[PASS]  * Assert eventlistener response ...[PASS] 2025/08/04 16:28:18 validating pipeline run pipelinerun-with-taskspec-to-echo-message for success state... 2025/08/04 16:28:28 pipelineRun: pipelinerun-with-taskspec-to-echo-message is successful under namespace : releasetest-czzgr  * Verify pipelinerun |S.NO|pipeline_run_name |status | |----|-----------------------------------------|----------| |1 |pipelinerun-with-taskspec-to-echo-message|successful| ...[PASS] 2025/08/04 16:28:28 Deleted EventListener 2025/08/04 16:28:33 EventListener's Deployment was deleted 2025/08/04 16:28:33 EventListener's Service was deleted 2025/08/04 16:28:33 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2025/08/04 16:30:03 output: project.project.openshift.io "releasetest-czzgr" deleted  ## Verify Github push event with Embbeded TriggerTemplate using Github-CTB: PIPELINES-05-TC12 2025/08/04 16:30:03 output: Now using project "releasetest-b6n56" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:30:08 output: triggertemplate.triggers.tekton.dev/pipeline-template-git-push created 2025/08/04 16:30:08 output: eventlistener.triggers.tekton.dev/listener-ctb-github-push created  * Create |S.NO|resource_dir | |----|------------------------------------------------------------------| |1 |testdata/triggers/github-ctb/Embeddedtriggertemplate-git-push.yaml| |2 |testdata/triggers/github-ctb/eventlistener-ctb-git-push.yaml | ...[PASS] 2025/08/04 16:30:09 triggertemplate pipeline-template-git-push exists  * Verify that "triggertemplate" "pipeline-template-git-push" exists ...[PASS] 2025/08/04 16:30:09 eventlistener listener-ctb-github-push exists  * Verify that "eventlistener" "listener-ctb-github-push" exists ...[PASS] 2025/08/04 16:30:09 output: secret/github-secret created 2025/08/04 16:30:09 output:  * Create & Link secret "github-secret" to service account "pipeline" ...[PASS] 2025/08/04 16:30:09 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:False Severity: LastTransitionTime:{Inner:2025-08-04 16:30:08 +0000 UTC} Reason:MinimumReplicasUnavailable Message:Deployment does not have minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:30:08 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:30:08 +0000 UTC} Reason:ReplicaSetUpdated Message:ReplicaSet "el-listener-ctb-github-push-7d5cb9749f" is progressing.} {Type:Ready Status:False Severity: LastTransitionTime:{Inner:2025-08-04 16:30:09 +0000 UTC} Reason: Message:Condition Available has status: False with message: Deployment does not have minimum availability.} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:30:09 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000e8c750 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-ctb-github-push}} 2025/08/04 16:30:14 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:30:10 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:30:10 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:30:10 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-listener-ctb-github-push-7d5cb9749f" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:30:10 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:30:10 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000a159b0 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-ctb-github-push}} 2025/08/04 16:30:14 sinkpod name: el-listener-ctb-github-push-7d5cb9749f-ck4gz 2025/08/04 16:30:14 Route url: 'http://el-listener-ctb-github-push-releasetest-b6n56.apps.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com'  * Expose Event listener "listener-ctb-github-push" ...[PASS] 2025/08/04 16:30:19 Building headers for github interceptor..  * Mock post event to "github" interceptor with event-type "push", payload "testdata/triggers/github-ctb/push.json", with TLS "false" ...[PASS]  * Assert eventlistener response ...[PASS] 2025/08/04 16:30:20 validating pipeline run pipelinerun-git-push-ctb for success state... 2025/08/04 16:30:25 pipelineRun: pipelinerun-git-push-ctb is successful under namespace : releasetest-b6n56  * Verify pipelinerun |S.NO|pipeline_run_name |status | |----|------------------------|----------| |1 |pipelinerun-git-push-ctb|successful| ...[PASS] 2025/08/04 16:30:25 Deleted EventListener 2025/08/04 16:30:30 EventListener's Deployment was deleted 2025/08/04 16:30:30 EventListener's Service was deleted 2025/08/04 16:30:30 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2025/08/04 16:32:00 output: project.project.openshift.io "releasetest-b6n56" deleted  ## Verify Github pull_request event with Embbeded TriggerTemplate using Github-CTB: PIPELINES-05-TC13 2025/08/04 16:32:00 output: Now using project "releasetest-554fw" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:32:05 output: triggertemplate.triggers.tekton.dev/pipeline-template-git-pr created 2025/08/04 16:32:05 output: eventlistener.triggers.tekton.dev/listener-clustertriggerbinding-github-pr created  * Create |S.NO|resource_dir | |----|----------------------------------------------------------------| |1 |testdata/triggers/github-ctb/Embeddedtriggertemplate-git-pr.yaml| |2 |testdata/triggers/github-ctb/eventlistener-ctb-git-pr.yaml | ...[PASS] 2025/08/04 16:32:05 triggertemplate pipeline-template-git-pr exists  * Verify that "triggertemplate" "pipeline-template-git-pr" exists ...[PASS] 2025/08/04 16:32:05 eventlistener listener-clustertriggerbinding-github-pr exists  * Verify that "eventlistener" "listener-clustertriggerbinding-github-pr" exists ...[PASS] 2025/08/04 16:32:06 clustertriggerbinding github-pullreq exists  * Verify that "clustertriggerbinding" "github-pullreq" exists ...[PASS] 2025/08/04 16:32:06 output: secret/github-secret created 2025/08/04 16:32:06 output:  * Create & Link secret "github-secret" to service account "pipeline" ...[PASS] 2025/08/04 16:32:06 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:False Severity: LastTransitionTime:{Inner:2025-08-04 16:32:05 +0000 UTC} Reason:MinimumReplicasUnavailable Message:Deployment does not have minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:32:05 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:32:05 +0000 UTC} Reason:ReplicaSetUpdated Message:ReplicaSet "el-listener-clustertriggerbinding-github-pr-5746d75c77" is progressing.} {Type:Ready Status:False Severity: LastTransitionTime:{Inner:2025-08-04 16:32:05 +0000 UTC} Reason: Message:Condition Available has status: False with message: Deployment does not have minimum availability.} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:32:05 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000771860 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-clustertriggerbinding-github-pr}} 2025/08/04 16:32:11 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:32:07 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:32:07 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:32:07 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-listener-clustertriggerbinding-github-pr-5746d75c77" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:32:07 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:32:07 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000743470 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-clustertriggerbinding-github-pr}} 2025/08/04 16:32:11 sinkpod name: el-listener-clustertriggerbinding-github-pr-5746d75c77-dq8mm 2025/08/04 16:32:11 Route url: 'http://el-listener-clustertriggerbinding-github-pr-releasetest-554fw.apps.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com'  * Expose Event listener "listener-clustertriggerbinding-github-pr" ...[PASS] 2025/08/04 16:32:16 Building headers for github interceptor..  * Mock post event to "github" interceptor with event-type "pull_request", payload "testdata/triggers/github-ctb/pr.json", with TLS "false" ...[PASS]  * Assert eventlistener response ...[PASS] 2025/08/04 16:32:17 validating pipeline run pipelinerun-git-pr-ctb for success state... 2025/08/04 16:32:27 pipelineRun: pipelinerun-git-pr-ctb is successful under namespace : releasetest-554fw  * Verify pipelinerun |S.NO|pipeline_run_name |status | |----|----------------------|----------| |1 |pipelinerun-git-pr-ctb|successful| ...[PASS] 2025/08/04 16:32:27 Deleted EventListener 2025/08/04 16:32:32 EventListener's Deployment was deleted 2025/08/04 16:32:32 EventListener's Service was deleted 2025/08/04 16:32:32 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2025/08/04 16:34:02 output: project.project.openshift.io "releasetest-554fw" deleted  ## Create TriggersCRD resource with CEL interceptors (overlays): PIPELINES-05-TC15 2025/08/04 16:34:02 output: Now using project "releasetest-8567p" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:34:07 output: eventlistener.triggers.tekton.dev/listener-triggerref created 2025/08/04 16:34:07 output: trigger.triggers.tekton.dev/trigger created 2025/08/04 16:34:07 output: triggerbinding.triggers.tekton.dev/github-pr-binding created 2025/08/04 16:34:07 output: triggertemplate.triggers.tekton.dev/github-template created 2025/08/04 16:34:08 output: pipeline.tekton.dev/parallel-pipeline created task.tekton.dev/persist-param created task.tekton.dev/to-upper created task.tekton.dev/to-lower created task.tekton.dev/result-reporter created task.tekton.dev/validator created  * Create |S.NO|resource_dir | |----|-----------------------------------------------------------| |1 |testdata/triggers/triggersCRD/eventlistener-triggerref.yaml| |2 |testdata/triggers/triggersCRD/trigger.yaml | |3 |testdata/triggers/triggersCRD/triggerbindings.yaml | |4 |testdata/triggers/triggersCRD/triggertemplate.yaml | |5 |testdata/triggers/triggersCRD/pipeline.yaml | ...[PASS] 2025/08/04 16:34:08 triggerbinding github-pr-binding exists  * Verify that "triggerbinding" "github-pr-binding" exists ...[PASS] 2025/08/04 16:34:08 triggertemplate github-template exists  * Verify that "triggertemplate" "github-template" exists ...[PASS] 2025/08/04 16:34:08 eventlistener listener-triggerref exists  * Verify that "eventlistener" "listener-triggerref" exists ...[PASS] 2025/08/04 16:34:08 output: secret/github-secret created 2025/08/04 16:34:08 output:  * Create & Link secret "github-secret" to service account "pipeline" ...[PASS] 2025/08/04 16:34:08 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:False Severity: LastTransitionTime:{Inner:2025-08-04 16:34:07 +0000 UTC} Reason:MinimumReplicasUnavailable Message:Deployment does not have minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:34:07 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:34:07 +0000 UTC} Reason:ReplicaSetUpdated Message:ReplicaSet "el-listener-triggerref-8f4955fbb" is progressing.} {Type:Ready Status:False Severity: LastTransitionTime:{Inner:2025-08-04 16:34:07 +0000 UTC} Reason: Message:Condition Available has status: False with message: Deployment does not have minimum availability.} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:34:07 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc00057bbf0 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-triggerref}} 2025/08/04 16:34:13 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:34:09 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:34:09 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:34:09 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-listener-triggerref-8f4955fbb" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:34:09 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:34:09 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000771020 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-triggerref}} 2025/08/04 16:34:13 sinkpod name: el-listener-triggerref-8f4955fbb-hwxxm 2025/08/04 16:34:14 Route url: 'http://el-listener-triggerref-releasetest-8567p.apps.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com'  * Expose Event listener "listener-triggerref" ...[PASS] 2025/08/04 16:34:19 Building headers for github interceptor..  * Mock post event to "github" interceptor with event-type "pull_request", payload "testdata/triggers/triggersCRD/pull-request.json", with TLS "false" ...[PASS]  * Assert eventlistener response ...[PASS] 2025/08/04 16:34:19 validating pipeline run parallel-pipelinerun for success state... 2025/08/04 16:35:04 pipelineRun: parallel-pipelinerun is successful under namespace : releasetest-8567p  * Verify pipelinerun |S.NO|pipeline_run_name |status | |----|--------------------|----------| |1 |parallel-pipelinerun|successful| ...[PASS] 2025/08/04 16:35:04 Deleted EventListener 2025/08/04 16:35:09 EventListener's Deployment was deleted 2025/08/04 16:35:09 EventListener's Service was deleted 2025/08/04 16:35:09 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2025/08/04 16:36:39 output: project.project.openshift.io "releasetest-8567p" deleted  ## Create Eventlistener with github interceptor And verify Kuberenetes Events: PIPELINES-05-TC17 2025/08/04 16:36:39 output: Now using project "releasetest-96qj7" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:36:45 output: task.tekton.dev/say-hello created task.tekton.dev/say-message created task.tekton.dev/say-bye created pipeline.tekton.dev/simple-pipeline created 2025/08/04 16:36:45 output: triggerbinding.triggers.tekton.dev/pipeline-binding created 2025/08/04 16:36:45 output: triggertemplate.triggers.tekton.dev/pipeline-template created 2025/08/04 16:36:45 output: eventlistener.triggers.tekton.dev/listener-embed-binding created  * Create |S.NO|resource_dir | |----|-------------------------------------------------------------------| |1 |testdata/triggers/sample-pipeline.yaml | |2 |testdata/triggers/triggerbindings/triggerbinding.yaml | |3 |testdata/triggers/triggertemplate/triggertemplate.yaml | |4 |testdata/triggers/eventlisteners/eventlistener-embeded-binding.yaml| ...[PASS] 2025/08/04 16:36:45 triggerbinding pipeline-binding exists  * Verify that "triggerbinding" "pipeline-binding" exists ...[PASS] 2025/08/04 16:36:45 triggertemplate pipeline-template exists  * Verify that "triggertemplate" "pipeline-template" exists ...[PASS] 2025/08/04 16:36:45 eventlistener listener-embed-binding exists  * Verify that "eventlistener" "listener-embed-binding" exists ...[PASS] 2025/08/04 16:36:45 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:False Severity: LastTransitionTime:{Inner:2025-08-04 16:36:45 +0000 UTC} Reason:MinimumReplicasUnavailable Message:Deployment does not have minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:36:45 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:36:45 +0000 UTC} Reason:ReplicaSetUpdated Message:ReplicaSet "el-listener-embed-binding-64745ccbf4" is progressing.} {Type:Ready Status:False Severity: LastTransitionTime:{Inner:2025-08-04 16:36:45 +0000 UTC} Reason: Message:Condition Available has status: False with message: Deployment does not have minimum availability.} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:36:45 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000ba2810 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-embed-binding}} 2025/08/04 16:36:50 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:36:46 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:36:46 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:36:46 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-listener-embed-binding-64745ccbf4" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:36:47 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:36:46 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000770660 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-embed-binding}} 2025/08/04 16:36:50 sinkpod name: el-listener-embed-binding-64745ccbf4-qqhc6 2025/08/04 16:36:51 Route url: 'http://el-listener-embed-binding-releasetest-96qj7.apps.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com'  * Expose Event listener "listener-embed-binding" ...[PASS] 2025/08/04 16:36:56 Building headers for github interceptor..  * Mock post event to "github" interceptor with event-type "push", payload "testdata/push.json", with TLS "false" ...[PASS]  * Assert eventlistener response ...[PASS]  * Verify kubernetes events for eventlistener ...[PASS] 2025/08/04 16:36:56 validating pipeline run simple-pipeline-run for success state... 2025/08/04 16:37:11 pipelineRun: simple-pipeline-run is successful under namespace : releasetest-96qj7  * Verify pipelinerun |S.NO|pipeline_run_name |status | |----|-------------------|----------| |1 |simple-pipeline-run|successful| ...[PASS] 2025/08/04 16:37:11 Deleted EventListener 2025/08/04 16:37:16 EventListener's Deployment was deleted 2025/08/04 16:37:16 EventListener's Service was deleted 2025/08/04 16:37:16 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2025/08/04 16:38:46 output: project.project.openshift.io "releasetest-96qj7" deleted # Verify triggerbindings spec  ## Verify CEL marshaljson function Test: PIPELINES-10-TC01 2025/08/04 16:38:46 output: Now using project "releasetest-d8ct4" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:38:52 output: eventlistener.triggers.tekton.dev/cel-marshaljson created  * Create |S.NO|resource_dir | |----|------------------------------------------------------| |1 |testdata/triggers/triggerbindings/cel-marshalJson.yaml| ...[PASS] 2025/08/04 16:38:52 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:38:52 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:38:52 +0000 UTC} Reason:NewReplicaSetCreated Message:Created new replica set "el-cel-marshaljson-5fdcf6b84c"} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:38:52 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:38:52 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000ba34a0 Addresses:[]} Configuration:{GeneratedResourceName:el-cel-marshaljson}} 2025/08/04 16:38:57 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:38:53 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:38:53 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:38:53 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-cel-marshaljson-5fdcf6b84c" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:38:53 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:38:53 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000a144e0 Addresses:[]} Configuration:{GeneratedResourceName:el-cel-marshaljson}} 2025/08/04 16:38:57 sinkpod name: el-cel-marshaljson-5fdcf6b84c-hct5s 2025/08/04 16:38:57 Route url: 'http://el-cel-marshaljson-releasetest-d8ct4.apps.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com'  * Expose Event listener "cel-marshaljson" ...[PASS] 2025/08/04 16:39:02 Building headers for github interceptor..  * Mock post event to "github" interceptor with event-type "push", payload "testdata/push.json", with TLS "false" ...[PASS]  * Assert eventlistener response ...[PASS] 2025/08/04 16:39:02 Waiting for TaskRun cel-trig-marshaljson in namespace releasetest-d8ct4 to succeed  * Verify taskrun |S.NO|task_run_name |status | |----|--------------------|-------| |1 |cel-trig-marshaljson|Success| ...[PASS] 2025/08/04 16:39:12 Deleted EventListener 2025/08/04 16:39:17 EventListener's Deployment was deleted 2025/08/04 16:39:17 EventListener's Service was deleted 2025/08/04 16:39:17 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2025/08/04 16:40:48 output: project.project.openshift.io "releasetest-d8ct4" deleted  ## Verify event message body parsing with old annotation Test: PIPELINES-10-TC02 2025/08/04 16:40:48 output: Now using project "releasetest-52n9f" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:40:53 output: triggertemplate.triggers.tekton.dev/taskrun-with-annotation created eventlistener.triggers.tekton.dev/parse-json-body-with-annotation created  * Create |S.NO|resource_dir | |----|----------------------------------------------------------------------| |1 |testdata/triggers/triggerbindings/parse-json-body-with-annotation.yaml| ...[PASS] 2025/08/04 16:40:53 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:40:53 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:40:53 +0000 UTC} Reason:NewReplicaSetCreated Message:Created new replica set "el-parse-json-body-with-annotation-8565f989dd"} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:40:53 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:40:53 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc0004176b0 Addresses:[]} Configuration:{GeneratedResourceName:el-parse-json-body-with-annotation}} 2025/08/04 16:40:58 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:40:54 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:40:54 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:40:54 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-parse-json-body-with-annotation-8565f989dd" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:40:54 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:40:54 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000892120 Addresses:[]} Configuration:{GeneratedResourceName:el-parse-json-body-with-annotation}} 2025/08/04 16:40:58 sinkpod name: el-parse-json-body-with-annotation-8565f989dd-szcnr 2025/08/04 16:40:59 Route url: 'http://el-parse-json-body-with-annotation-releasetest-52n9f.apps.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com'  * Expose Event listener "parse-json-body-with-annotation" ...[PASS] 2025/08/04 16:41:04 Building headers for github interceptor..  * Mock post event to "github" interceptor with event-type "push", payload "testdata/push.json", with TLS "false" ...[PASS]  * Assert eventlistener response ...[PASS] 2025/08/04 16:41:04 Waiting for TaskRun trig-parse-json-body-with-annotation in namespace releasetest-52n9f to succeed  * Verify taskrun |S.NO|task_run_name |status | |----|------------------------------------|-------| |1 |trig-parse-json-body-with-annotation|Success| ...[PASS] 2025/08/04 16:41:09 Deleted EventListener 2025/08/04 16:41:14 EventListener's Deployment was deleted 2025/08/04 16:41:14 EventListener's Service was deleted 2025/08/04 16:41:14 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2025/08/04 16:42:44 output: project.project.openshift.io "releasetest-52n9f" deleted # Verify triggers tutorial  ## Run pipelines tutorial using triggers: PIPELINES-06-TC02 2025/08/04 16:42:44 output: Now using project "releasetest-wbwdk" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:42:49 output: task.tekton.dev/apply-manifests created 2025/08/04 16:42:50 output: task.tekton.dev/update-deployment created 2025/08/04 16:42:50 output: persistentvolumeclaim/source-pvc created 2025/08/04 16:42:50 output: pipeline.tekton.dev/build-and-deploy created 2025/08/04 16:42:50 output: triggerbinding.triggers.tekton.dev/vote-app created 2025/08/04 16:42:51 output: triggertemplate.triggers.tekton.dev/vote-app created 2025/08/04 16:42:51 output: trigger.triggers.tekton.dev/vote-trigger created secret/github-secret created 2025/08/04 16:42:51 output: eventlistener.triggers.tekton.dev/vote-app created  * Create remote |S.NO|resource_dir | |----|--------------------------------------------------------------------------------------------------------------------------------| |1 |https://raw.githubusercontent.com/openshift/pipelines-tutorial/{OSP_TUTORIAL_BRANCH}/01_pipeline/01_apply_manifest_task.yaml | |2 |https://raw.githubusercontent.com/openshift/pipelines-tutorial/{OSP_TUTORIAL_BRANCH}/01_pipeline/02_update_deployment_task.yaml | |3 |https://raw.githubusercontent.com/openshift/pipelines-tutorial/{OSP_TUTORIAL_BRANCH}/01_pipeline/03_persistent_volume_claim.yaml| |4 |https://raw.githubusercontent.com/openshift/pipelines-tutorial/{OSP_TUTORIAL_BRANCH}/01_pipeline/04_pipeline.yaml | |5 |https://raw.githubusercontent.com/openshift/pipelines-tutorial/{OSP_TUTORIAL_BRANCH}/03_triggers/01_binding.yaml | |6 |https://raw.githubusercontent.com/openshift/pipelines-tutorial/{OSP_TUTORIAL_BRANCH}/03_triggers/02_template.yaml | |7 |https://raw.githubusercontent.com/openshift/pipelines-tutorial/{OSP_TUTORIAL_BRANCH}/03_triggers/03_trigger.yaml | |8 |https://raw.githubusercontent.com/openshift/pipelines-tutorial/{OSP_TUTORIAL_BRANCH}/03_triggers/04_event_listener.yaml | ...[PASS] 2025/08/04 16:42:51 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:42:51 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:42:51 +0000 UTC} Reason:NewReplicaSetCreated Message:Created new replica set "el-vote-app-57f9fb9c6"} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:42:51 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:42:51 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000aa8510 Addresses:[]} Configuration:{GeneratedResourceName:el-vote-app}} 2025/08/04 16:42:56 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:42:53 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:42:53 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:42:53 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-vote-app-57f9fb9c6" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:42:53 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2025-08-04 16:42:53 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000aa82d0 Addresses:[]} Configuration:{GeneratedResourceName:el-vote-app}} 2025/08/04 16:42:56 sinkpod name: el-vote-app-57f9fb9c6-7xmj8 2025/08/04 16:42:57 Route url: 'http://el-vote-app-releasetest-wbwdk.apps.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com'  * Expose Event listener "vote-app" ...[PASS] 2025/08/04 16:43:02 Building headers for github interceptor..  * Mock post event to "github" interceptor with event-type "push", payload "testdata/push-vote-api.json", with TLS "false" ...[PASS]  * Assert eventlistener response ...[PASS] 2025/08/04 16:43:02 Verifying if 1 pipelineruns are present  * "1" pipelinerun(s) should be present within "15" seconds ...[PASS] 2025/08/04 16:43:07 validating pipeline run build-deploy-pipelines-vote-api-rg8hv for success state... 2025/08/04 16:44:52 pipelineRun: build-deploy-pipelines-vote-api-rg8hv is successful under namespace : releasetest-wbwdk  * Verify the latest pipelinerun for "successful" state ...[PASS] 2025/08/04 16:44:52 Building headers for github interceptor..  * Mock post event to "github" interceptor with event-type "push", payload "testdata/push-vote-ui.json", with TLS "false" ...[PASS]  * Assert eventlistener response ...[PASS] 2025/08/04 16:44:52 Verifying if 2 pipelineruns are present  * "2" pipelinerun(s) should be present within "15" seconds ...[PASS] 2025/08/04 16:44:57 validating pipeline run build-deploy-pipelines-vote-ui-p2p8x for success state... 2025/08/04 16:46:27 pipelineRun: build-deploy-pipelines-vote-ui-p2p8x is successful under namespace : releasetest-wbwdk  * Verify the latest pipelinerun for "successful" state ...[PASS] 2025/08/04 16:46:27 Route url: 'http://pipelines-vote-ui-releasetest-wbwdk.apps.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com'  * Get route url of the route "pipelines-vote-ui" ...[PASS]  * Wait for "pipelines-vote-ui" deployment ...[PASS]  * Validate that route URL contains "Cat 🐺 vs Dog 🐶" ...[FAIL]  Failed Step: Validate that route URL contains "Cat 🐺 vs Dog 🐶" Specification: specs/triggers/tutorial.spec:68 Error Message: expected: Cat 🐺 vs Dog 🐶, got:

Application is not available

The application is currently not serving requests at this endpoint. It may not have been started or is still starting.

Possible reasons you are seeing this page:

Stacktrace: /alabama/go/pkg/mod/github.com/getgauge-contrib/gauge-go@v0.4.0/testsuit/testing.go:46 github.com/openshift-pipelines/release-tests/steps/utility.init.func4({0xc0006cf0e0, 0x14}) /tmp/release-tests/steps/utility/utility.go:49 +0x205 reflect.Value.call({0x3bbd480?, 0x44d1330?, 0xc000045b18?}, {0x434b23d, 0x4}, {0xc000800f18, 0x1, 0x0?}) /usr/lib/golang/src/reflect/value.go:584 +0xca6 reflect.Value.Call({0x3bbd480?, 0x44d1330?, 0x10?}, {0xc000800f18?, 0x179f601?, 0x10?}) /usr/lib/golang/src/reflect/value.go:368 +0xb9 github.com/getgauge-contrib/gauge-go/testsuit.executeFunc({0x3bbd480?, 0x44d1330?, 0x60?}, {0xc000b53940, 0x1, 0x7d?}) /alabama/go/pkg/mod/github.com/getgauge-contrib/gauge-go@v0.4.0/testsuit/funcExecutor.go:47 +0x20d github.com/getgauge-contrib/gauge-go/testsuit.(*Step).Execute(0xc00025c7e0?, {0xc000b53940?, 0x23?, 0x7f?}) /alabama/go/pkg/mod/github.com/getgauge-contrib/gauge-go@v0.4.0/testsuit/step.go:17 +0x7d github.com/getgauge-contrib/gauge-go/messageprocessors.(*ExecuteStepProcessor).Process(0x3f0e500?, 0xc000b1a4b0, 0xc000000007?) /alabama/go/pkg/mod/github.com/getgauge-contrib/gauge-go@v0.4.0/messageprocessors/ExecuteStepProcessor.go:20 +0x9f github.com/getgauge-contrib/gauge-go/gauge.Run() /alabama/go/pkg/mod/github.com/getgauge-contrib/gauge-go@v0.4.0/gauge/runner.go:219 +0x20e command-line-arguments.init.0() /tmp/gauge_temp1754324273082054467/gauge_test.go:37 +0xf 2025/08/04 16:46:57 Skipping deletion of the namespace 'releasetest-wbwdk' as the test got failed Transformed SuiteResult to report structure Successfully generated html-report to => /logs/artifacts/html-report/2025-08-04_16.46.57/index.html Done generating HTML report using theme from /tmp/plugins/html-report/4.3.3/themes/default Successfully generated xml-report to => /logs/artifacts/xml-report/2025-08-04 16.46.57 Sending kill message to Xml Report plugin. Sending kill message to Html Report plugin. Sending kill message to runner. ok command-line-arguments 1740.135s Runner with PID:23835 has exited Specifications: 4 executed 3 passed 1 failed 0 skipped Scenarios: 10 executed 9 passed 1 failed 0 skipped Total time taken: 29m0.047s Updates are available. Run `gauge update -c` for more info. gauge run specs/metrics/ log-level : [debug] tags : [sanity & !tls] verbose : [true] env will be loaded from default directory 'env' 'gauge_environment' set to 'default' Created gauge_screenshots_dir at /tmp/release-tests/.gauge/screenshots Plugin go is already installed. Plugin html-report is already installed. Plugin xml-report is already installed. Parsing started. Started concepts parsing. 14 concepts parsing completed. Started specifications parsing. 1 specifications parsing completed. Applying tags filter: sanity & !tls The following specifications satisfy filter criteria: specs/metrics/metrics.spec Parsing completed. Starting go runner Checking updates... Downloading https://downloads.gauge.org/plugin/go?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Downloading https://downloads.gauge.org/plugin/html-report?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Downloading https://downloads.gauge.org/plugin/xml-report?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Established connection to runner. Validation started. Validation completed. Run started Starting Html Report plugin Setting MaxRecvMsgSize = 1024 MB Attempting to connect to grpc server at port: 43263 Successfully made the connection with plugin with port: 43263 Starting Xml Report plugin Attempting to connect to grpc server at port: 45669 Successfully made the connection with plugin with port: 45669 Initialising suite data store. # Verify openshift pipelines monitoring  ## Openshift pipelines metrics acceptance tests: PIPELINES-01-TC01 2025/08/04 16:47:03 output: Now using project "releasetest-sf6rw" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname 2025/08/04 16:47:08 Waiting for operator to be up and running.... 2025/08/04 16:47:08 Operator is up  * Validate Operator should be installed ...[PASS] 2025/08/04 16:47:09 Target Job: [node-exporter] ready/up status, Actual: [1], Expected: [1] 2025/08/04 16:47:09 Target Job: [kube-state-metrics] ready/up status, Actual: [1], Expected: [1] 2025/08/04 16:47:09 Target Job: [prometheus-k8s] ready/up status, Actual: [1], Expected: [1] 2025/08/04 16:47:09 Target Job: [prometheus-operator] ready/up status, Actual: [1], Expected: [1] 2025/08/04 16:47:09 Target Job: [alertmanager-main] ready/up status, Actual: [1], Expected: [1] 2025/08/04 16:47:09 Target Job: [tekton-pipelines-controller] ready/up status, Actual: [1], Expected: [1]  * Verify job health status metrics |S.NO|Job_name |Expected_value| |----|---------------------------|--------------| |1 |node-exporter |1 | |2 |kube-state-metrics |1 | |3 |prometheus-k8s |1 | |4 |prometheus-operator |1 | |5 |alertmanager-main |1 | |6 |tekton-pipelines-controller|1 | ...[PASS]  * Verify pipelines controlPlane metrics ...[PASS] 2025/08/04 16:47:17 output: project.project.openshift.io "releasetest-sf6rw" deleted Transformed SuiteResult to report structure Successfully generated html-report to => /logs/artifacts/html-report/2025-08-04_16.47.17/index.html Done generating HTML report using theme from /tmp/plugins/html-report/4.3.3/themes/default Successfully generated xml-report to => /logs/artifacts/xml-report/2025-08-04 16.47.17 Sending kill message to Html Report plugin. Sending kill message to Xml Report plugin. Sending kill message to runner. ok command-line-arguments 13.920s Runner with PID:26970 has exited Specifications: 1 executed 1 passed 0 failed 0 skipped Scenarios: 1 executed 1 passed 0 failed 0 skipped Total time taken: 13.846s Updates are available. Run `gauge update -c` for more info. gauge run specs/operator/addon.spec log-level : [debug] tags : [sanity & !tls] verbose : [true] env will be loaded from default directory 'env' 'gauge_environment' set to 'default' Created gauge_screenshots_dir at /tmp/release-tests/.gauge/screenshots Plugin go is already installed. Plugin html-report is already installed. Plugin xml-report is already installed. Parsing started. Started concepts parsing. 14 concepts parsing completed. Started specifications parsing. 1 specifications parsing completed. Applying tags filter: sanity & !tls The following specifications satisfy filter criteria: specs/operator/addon.spec Parsing completed. Starting go runner Checking updates... Downloading https://downloads.gauge.org/plugin/go?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Downloading https://downloads.gauge.org/plugin/html-report?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Downloading https://downloads.gauge.org/plugin/xml-report?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Established connection to runner. Validation started. Validation completed. Run started Starting Html Report plugin Setting MaxRecvMsgSize = 1024 MB Attempting to connect to grpc server at port: 38591 Successfully made the connection with plugin with port: 38591 Starting Xml Report plugin Attempting to connect to grpc server at port: 37221 Successfully made the connection with plugin with port: 37221 Initialising suite data store. # Verify Addon E2E spec  ## Disable/Enable resolverTasks: PIPELINES-15-TC06 2025/08/04 16:47:23 output: Now using project "releasetest-twmkj" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname 2025/08/04 16:47:28 Waiting for operator to be up and running.... 2025/08/04 16:47:28 Operator is up  * Validate Operator should be installed ...[PASS] 2025/08/04 16:47:28 output: tektonconfig.operator.tekton.dev/config patched  * Update addon config with resolverTasks as "false" and expect message "" ...[PASS] 2025/08/04 16:47:28 Checking if tasks s2i-java is/are not present in namespace openshift-pipelines 2025/08/04 16:47:33 Verifying if the task s2i-java is not present 2025/08/04 16:47:33 Task s2i-java is not present  * Tasks "s2i-java" are "not present" in namespace "openshift-pipelines" ...[PASS] 2025/08/04 16:47:33 output: tektonconfig.operator.tekton.dev/config patched  * Update addon config with resolverTasks as "true" and expect message "" ...[PASS] 2025/08/04 16:47:33 Checking if tasks s2i-java is/are present in namespace openshift-pipelines 2025/08/04 16:47:38 Verifying if the task s2i-java is present 2025/08/04 16:47:38 Task s2i-java is present  * Tasks "s2i-java" are "present" in namespace "openshift-pipelines" ...[PASS] 2025/08/04 16:47:45 output: project.project.openshift.io "releasetest-twmkj" deleted  ## Disable/Enable pipeline templates: PIPELINES-15-TC08 2025/08/04 16:47:46 output: Now using project "releasetest-td5tr" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:47:51 output: tektonconfig.operator.tekton.dev/config patched  * Update addon config with resolverTasks as "true" and pipelineTemplates as "true" and expect message "" ...[PASS] 2025/08/04 16:47:56 Verifying that 27 pipelines are present in namespace openshift 2025/08/04 16:47:56 Pipelines are present in namespace openshift  * Assert pipelines are "present" in "openshift" namespace ...[PASS] 2025/08/04 16:47:56 output: tektonconfig.operator.tekton.dev/config patched  * Update addon config with resolverTasks as "true" and pipelineTemplates as "false" and expect message "" ...[PASS] 2025/08/04 16:48:01 Verifying if 0 pipelines are not present in namespace openshift 2025/08/04 16:48:01 Pipelines are present in namespace openshift  * Assert pipelines are "not present" in "openshift" namespace ...[PASS] 2025/08/04 16:48:01 output: tektonconfig.operator.tekton.dev/config patched  * Update addon config with resolverTasks as "true" and pipelineTemplates as "true" and expect message "" ...[PASS] 2025/08/04 16:48:06 Verifying that 27 pipelines are present in namespace openshift 2025/08/04 16:48:06 Pipelines are present in namespace openshift  * Assert pipelines are "present" in "openshift" namespace ...[PASS] 2025/08/04 16:48:14 output: project.project.openshift.io "releasetest-td5tr" deleted Transformed SuiteResult to report structure Successfully generated html-report to => /logs/artifacts/html-report/2025-08-04_16.48.14/index.html Done generating HTML report using theme from /tmp/plugins/html-report/4.3.3/themes/default Successfully generated xml-report to => /logs/artifacts/xml-report/2025-08-04 16.48.14 Sending kill message to Html Report plugin. Sending kill message to Xml Report plugin. Sending kill message to runner. ok command-line-arguments 51.284s Runner with PID:27540 has exited Specifications: 1 executed 1 passed 0 failed 0 skipped Scenarios: 2 executed 2 passed 0 failed 0 skipped Total time taken: 51.204s Updates are available. Run `gauge update -c` for more info. gauge run specs/operator/auto-prune.spec log-level : [debug] tags : [sanity & !tls] verbose : [true] env will be loaded from default directory 'env' 'gauge_environment' set to 'default' Created gauge_screenshots_dir at /tmp/release-tests/.gauge/screenshots Plugin go is already installed. Plugin html-report is already installed. Plugin xml-report is already installed. Parsing started. Started concepts parsing. 14 concepts parsing completed. Started specifications parsing. 1 specifications parsing completed. Applying tags filter: sanity & !tls The following specifications satisfy filter criteria: specs/operator/auto-prune.spec Parsing completed. Starting go runner Checking updates... Downloading https://downloads.gauge.org/plugin/go?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Downloading https://downloads.gauge.org/plugin/html-report?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Downloading https://downloads.gauge.org/plugin/xml-report?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Established connection to runner. Validation started. Validation completed. Run started Starting Html Report plugin Setting MaxRecvMsgSize = 1024 MB Attempting to connect to grpc server at port: 38815 Successfully made the connection with plugin with port: 38815 Starting Xml Report plugin Attempting to connect to grpc server at port: 36781 Successfully made the connection with plugin with port: 36781 Initialising suite data store. # Verify auto-prune E2E 2025/08/04 16:48:19 output: Now using project "releasetest-khxc8" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname 2025/08/04 16:48:19 Annotating the namespaces with 'operator.tekton.dev/prune.skip=true' so that the pipelineruns should not get deleted 2025/08/04 16:48:19 output: namespace/openshift annotated 2025/08/04 16:48:20 output: namespace/releasetest-khxc8 annotated 2025/08/04 16:48:20 output: namespace/releasetest-pipelines annotated 2025/08/04 16:48:20 output: namespace/releasetest-tasks annotated 2025/08/04 16:48:20 output: namespace/releasetest-wbwdk annotated  ## Verify auto prune for taskrun: PIPELINES-12-TC01 2025/08/04 16:48:20 output: Now using project "releasetest-km7km" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname 2025/08/04 16:48:25 Waiting for operator to be up and running.... 2025/08/04 16:48:25 Operator is up  * Validate Operator should be installed ...[PASS] 2025/08/04 16:48:25 Removing pruner configuration from config CR  * Remove auto pruner configuration from config CR ...[PASS] 2025/08/04 16:48:26 output: task.tekton.dev/echo-task-pipeline created pipeline.tekton.dev/echo-pipeline created 2025/08/04 16:48:26 output: pipelinerun.tekton.dev/echo-pipeline-run-sq8w2 created pipelinerun.tekton.dev/echo-pipeline-run-gd2td created pipelinerun.tekton.dev/echo-pipeline-run-mp4rv created pipelinerun.tekton.dev/echo-pipeline-run-mjfsx created pipelinerun.tekton.dev/echo-pipeline-run-98l8p created 2025/08/04 16:48:27 output: task.tekton.dev/echo-task created 2025/08/04 16:48:27 output: taskrun.tekton.dev/echo-task-run-tj5rp created taskrun.tekton.dev/echo-task-run-pswsw created taskrun.tekton.dev/echo-task-run-z69nd created taskrun.tekton.dev/echo-task-run-mr4vp created taskrun.tekton.dev/echo-task-run-wnh4p created  * Create |S.NO|resource_dir | |----|----------------------------------------------------| |1 |testdata/pruner/pipeline/pipeline-for-pruner.yaml | |2 |testdata/pruner/pipeline/pipelinerun-for-pruner.yaml| |3 |testdata/pruner/task/task-for-pruner.yaml | |4 |testdata/pruner/task/taskrun-for-pruner.yaml | ...[PASS] 2025/08/04 16:48:27 output: tektonconfig.operator.tekton.dev/config patched  * Update pruner config "with" keep "2" schedule "*/1 * * * *" resources "taskrun" and "without" keep-since "" ...[PASS] 2025/08/04 16:48:27 Verifying if the cronjob tekton-resource-pruner is present in namespace openshift-pipelines 2025/08/04 16:48:32 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2025/08/04 16:48:32 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines  * Assert if cronjob with prefix "tekton-resource-pruner" is "present" in target namespace ...[PASS] 2025/08/04 16:48:32 Verifying if 2 taskruns are present  * "2" taskrun(s) should be present within "180" seconds ...[PASS] 2025/08/04 16:51:12 Verifying if 5 pipelineruns are present  * "5" pipelinerun(s) should be present within "120" seconds ...[PASS] 2025/08/04 16:51:17 Removing pruner configuration from config CR  * Remove auto pruner configuration from config CR ...[PASS] 2025/08/04 16:51:17 Verifying if the cronjob tekton-resource-pruner is not present in namespace openshift-pipelines 2025/08/04 16:51:22 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2025/08/04 16:51:22 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines  * Assert if cronjob with prefix "tekton-resource-pruner" is "not present" in target namespace ...[PASS] 2025/08/04 16:51:37 output: project.project.openshift.io "releasetest-km7km" deleted  ## Verify auto prune with keep-since: PIPELINES-12-TC04 2025/08/04 16:51:37 output: Now using project "releasetest-ktzr8" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:51:42 Removing pruner configuration from config CR  * Remove auto pruner configuration from config CR ...[PASS] 2025/08/04 16:51:43 output: task.tekton.dev/echo-task-pipeline created pipeline.tekton.dev/echo-pipeline created 2025/08/04 16:51:43 output: pipelinerun.tekton.dev/echo-pipeline-run-d6spg created pipelinerun.tekton.dev/echo-pipeline-run-cqcwg created pipelinerun.tekton.dev/echo-pipeline-run-zpmbp created pipelinerun.tekton.dev/echo-pipeline-run-964lq created pipelinerun.tekton.dev/echo-pipeline-run-9m897 created 2025/08/04 16:51:43 output: task.tekton.dev/echo-task created 2025/08/04 16:51:43 output: taskrun.tekton.dev/echo-task-run-t8rst created taskrun.tekton.dev/echo-task-run-ff47r created taskrun.tekton.dev/echo-task-run-6dvjj created taskrun.tekton.dev/echo-task-run-r7x5l created taskrun.tekton.dev/echo-task-run-r4fck created  * Create |S.NO|resource_dir | |----|----------------------------------------------------| |1 |testdata/pruner/pipeline/pipeline-for-pruner.yaml | |2 |testdata/pruner/pipeline/pipelinerun-for-pruner.yaml| |3 |testdata/pruner/task/task-for-pruner.yaml | |4 |testdata/pruner/task/taskrun-for-pruner.yaml | ...[PASS] 2025/08/04 16:51:43 Sleeping for 120 seconds  * Sleep for "120" seconds ...[PASS] 2025/08/04 16:53:44 output: pipelinerun.tekton.dev/echo-pipeline-run-l4pqr created pipelinerun.tekton.dev/echo-pipeline-run-vggzw created pipelinerun.tekton.dev/echo-pipeline-run-zn774 created pipelinerun.tekton.dev/echo-pipeline-run-86pgw created pipelinerun.tekton.dev/echo-pipeline-run-7w7mz created 2025/08/04 16:53:44 output: taskrun.tekton.dev/echo-task-run-rzzzm created taskrun.tekton.dev/echo-task-run-p7jk8 created taskrun.tekton.dev/echo-task-run-n6tbb created taskrun.tekton.dev/echo-task-run-dzk7p created taskrun.tekton.dev/echo-task-run-qdv6s created  * Create |S.NO|resource_dir | |----|----------------------------------------------------| |1 |testdata/pruner/pipeline/pipelinerun-for-pruner.yaml| |2 |testdata/pruner/task/taskrun-for-pruner.yaml | ...[PASS] 2025/08/04 16:53:44 output: tektonconfig.operator.tekton.dev/config patched  * Update pruner config "without" keep "" schedule "*/1 * * * *" resources "pipelinerun,taskrun" and "with" keep-since "2" ...[PASS] 2025/08/04 16:53:44 Verifying if the cronjob tekton-resource-pruner is present in namespace openshift-pipelines 2025/08/04 16:53:49 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2025/08/04 16:53:49 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines  * Assert if cronjob with prefix "tekton-resource-pruner" is "present" in target namespace ...[PASS] 2025/08/04 16:53:49 Verifying if 5 pipelineruns are present  * "5" pipelinerun(s) should be present within "120" seconds ...[PASS] 2025/08/04 16:54:04 Verifying if 10 taskruns are present  * "10" taskrun(s) should be present within "180" seconds ...[PASS] 2025/08/04 16:54:24 Removing pruner configuration from config CR  * Remove auto pruner configuration from config CR ...[PASS] 2025/08/04 16:54:25 Verifying if the cronjob tekton-resource-pruner is not present in namespace openshift-pipelines 2025/08/04 16:54:30 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2025/08/04 16:54:30 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines  * Assert if cronjob with prefix "tekton-resource-pruner" is "not present" in target namespace ...[PASS] 2025/08/04 16:56:00 output: project.project.openshift.io "releasetest-ktzr8" deleted  ## Verify auto prune add resources taskrun and pipelinerun per namespace with annotation: PIPELINES-12-TC07 2025/08/04 16:56:00 output: Now using project "releasetest-6znpw" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 16:56:05 Removing pruner configuration from config CR  * Remove auto pruner configuration from config CR ...[PASS] 2025/08/04 16:56:05 output: task.tekton.dev/echo-task-pipeline created pipeline.tekton.dev/echo-pipeline created 2025/08/04 16:56:05 output: pipelinerun.tekton.dev/echo-pipeline-run-gq4pk created pipelinerun.tekton.dev/echo-pipeline-run-nh8kg created pipelinerun.tekton.dev/echo-pipeline-run-vxp8j created pipelinerun.tekton.dev/echo-pipeline-run-m59kd created pipelinerun.tekton.dev/echo-pipeline-run-hxpkq created 2025/08/04 16:56:05 output: task.tekton.dev/echo-task created 2025/08/04 16:56:06 output: taskrun.tekton.dev/echo-task-run-72h96 created taskrun.tekton.dev/echo-task-run-z2n6p created taskrun.tekton.dev/echo-task-run-fl9jg created taskrun.tekton.dev/echo-task-run-4c2jl created taskrun.tekton.dev/echo-task-run-hss74 created  * Create |S.NO|resource_dir | |----|----------------------------------------------------| |1 |testdata/pruner/pipeline/pipeline-for-pruner.yaml | |2 |testdata/pruner/pipeline/pipelinerun-for-pruner.yaml| |3 |testdata/pruner/task/task-for-pruner.yaml | |4 |testdata/pruner/task/taskrun-for-pruner.yaml | ...[PASS] 2025/08/04 16:56:06 Annotating namespace releasetest-6znpw with operator.tekton.dev/prune.resources=pipelinerun,taskrun 2025/08/04 16:56:06 output: namespace/releasetest-6znpw annotated  * Annotate namespace with "operator.tekton.dev/prune.resources=pipelinerun,taskrun" ...[PASS] 2025/08/04 16:56:06 output: tektonconfig.operator.tekton.dev/config patched  * Update pruner config "with" keep "2" schedule "*/1 * * * *" resources "taskrun" and "without" keep-since "" ...[PASS] 2025/08/04 16:56:06 Verifying if the cronjob tekton-resource-pruner is present in namespace openshift-pipelines 2025/08/04 16:56:11 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2025/08/04 16:56:11 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines  * Assert if cronjob with prefix "tekton-resource-pruner" is "present" in target namespace ...[PASS] 2025/08/04 16:56:11 Verifying if 2 pipelineruns are present  * "2" pipelinerun(s) should be present within "120" seconds ...[PASS] 2025/08/04 16:57:06 Verifying if 2 taskruns are present  * "2" taskrun(s) should be present within "180" seconds ...[PASS] 2025/08/04 16:58:56 Removing annotation releasetest-6znpw from namespace operator.tekton.dev/prune.resources 2025/08/04 16:58:56 output: namespace/releasetest-6znpw annotated  * Remove annotation "operator.tekton.dev/prune.resources" from namespace ...[PASS] 2025/08/04 16:58:56 output: pipelinerun.tekton.dev/echo-pipeline-run-km2jf created pipelinerun.tekton.dev/echo-pipeline-run-knnv7 created pipelinerun.tekton.dev/echo-pipeline-run-jm2fk created pipelinerun.tekton.dev/echo-pipeline-run-xgwqq created pipelinerun.tekton.dev/echo-pipeline-run-j2dlp created 2025/08/04 16:58:57 output: taskrun.tekton.dev/echo-task-run-ccwbd created taskrun.tekton.dev/echo-task-run-rrxqn created taskrun.tekton.dev/echo-task-run-5rjrq created taskrun.tekton.dev/echo-task-run-7575s created taskrun.tekton.dev/echo-task-run-txvnz created  * Create |S.NO|resource_dir | |----|----------------------------------------------------| |1 |testdata/pruner/pipeline/pipelinerun-for-pruner.yaml| |2 |testdata/pruner/task/taskrun-for-pruner.yaml | ...[PASS] 2025/08/04 16:58:57 Verifying if 7 pipelineruns are present  * "7" pipelinerun(s) should be present within "120" seconds ...[PASS] 2025/08/04 16:59:02 Verifying if 2 taskruns are present  * "2" taskrun(s) should be present within "180" seconds ...[PASS] 2025/08/04 17:01:42 Removing pruner configuration from config CR  * Remove auto pruner configuration from config CR ...[PASS] 2025/08/04 17:01:42 Verifying if the cronjob tekton-resource-pruner is not present in namespace openshift-pipelines 2025/08/04 17:01:47 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2025/08/04 17:01:47 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines  * Assert if cronjob with prefix "tekton-resource-pruner" is "not present" in target namespace ...[PASS] 2025/08/04 17:02:05 output: project.project.openshift.io "releasetest-6znpw" deleted  ## Verify auto prune cronjob contains single container: PIPELINES-12-TC14 2025/08/04 17:02:05 output: Now using project "releasetest-tm4dj" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 17:02:11 output: tektonconfig.operator.tekton.dev/config patched  * Update pruner config "with" keep "2" schedule "20 * * * *" resources "taskrun" and "without" keep-since "" ...[PASS] 2025/08/04 17:02:11 Check if project test-project-1 already exists 2025/08/04 17:02:11 Creating project test-project-1 2025/08/04 17:02:11 output: Now using project "test-project-1" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Create project "test-project-1" ...[PASS] 2025/08/04 17:02:11 Check if project test-project-2 already exists 2025/08/04 17:02:11 Creating project test-project-2 2025/08/04 17:02:11 output: Now using project "test-project-2" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Create project "test-project-2" ...[PASS] 2025/08/04 17:02:11 Sleeping for 10 seconds  * Sleep for "10" seconds ...[PASS] 2025/08/04 17:02:21 Verifying if the cronjob with prefix tekton-resource-pruner in namespace openshift-pipelines contains 1 number of containers 2025/08/04 17:02:21 1 containers found in the cronjob spec  * Assert pruner cronjob(s) in namespace "target namespace" contains "1" number of container(s) ...[PASS] 2025/08/04 17:02:21 Deleting project test-project-1 2025/08/04 17:02:29 output: project.project.openshift.io "test-project-1" deleted  * Delete project "test-project-1" ...[PASS] 2025/08/04 17:02:29 Deleting project test-project-2 2025/08/04 17:02:37 output: project.project.openshift.io "test-project-2" deleted  * Delete project "test-project-2" ...[PASS] 2025/08/04 17:02:37 Removing pruner configuration from config CR  * Remove auto pruner configuration from config CR ...[PASS] 2025/08/04 17:02:45 output: project.project.openshift.io "releasetest-tm4dj" deleted  ## Verify that the operator is up and running after deleting namespace with pruner annotation: PIPELINES-12-TC15 2025/08/04 17:02:45 output: Now using project "releasetest-qlht4" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname  * Validate Operator should be installed ...[PASS] 2025/08/04 17:02:50 Removing pruner configuration from config CR  * Remove auto pruner configuration from config CR ...[PASS] 2025/08/04 17:02:50 Verifying if the cronjob tekton-resource-pruner is not present in namespace openshift-pipelines 2025/08/04 17:02:55 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2025/08/04 17:02:55 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines  * Assert if cronjob with prefix "tekton-resource-pruner" is "not present" in target namespace ...[PASS] 2025/08/04 17:02:55 output: namespace/namespace-one created  * Create |S.NO|resource_dir | |----|---------------------------------------------| |1 |testdata/pruner/namespaces/namespace-one.yaml| ...[PASS] 2025/08/04 17:02:55 Verifying if the cronjob tekton-resource-pruner is present in namespace openshift-pipelines 2025/08/04 17:03:00 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2025/08/04 17:03:00 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines  * Assert if cronjob with prefix "tekton-resource-pruner" is "present" in target namespace ...[PASS] 2025/08/04 17:03:00 Deleting project namespace-one 2025/08/04 17:03:08 output: project.project.openshift.io "namespace-one" deleted  * Delete project "namespace-one" ...[PASS] 2025/08/04 17:03:08 Sleeping for 5 seconds  * Sleep for "5" seconds ...[PASS] 2025/08/04 17:03:13 Verifying if the cronjob tekton-resource-pruner is not present in namespace openshift-pipelines 2025/08/04 17:03:18 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2025/08/04 17:03:18 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines  * Assert if cronjob with prefix "tekton-resource-pruner" is "not present" in target namespace ...[PASS]  * Validate Operator should be installed ...[PASS] 2025/08/04 17:03:18 output: namespace/namespace-two created  * Create |S.NO|resource_dir | |----|---------------------------------------------| |1 |testdata/pruner/namespaces/namespace-two.yaml| ...[PASS] 2025/08/04 17:03:18 Verifying if the cronjob tekton-resource-pruner is present in namespace openshift-pipelines 2025/08/04 17:03:23 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2025/08/04 17:03:23 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines  * Assert if cronjob with prefix "tekton-resource-pruner" is "present" in target namespace ...[PASS] 2025/08/04 17:03:23 Deleting project namespace-two 2025/08/04 17:03:31 output: project.project.openshift.io "namespace-two" deleted  * Delete project "namespace-two" ...[PASS] 2025/08/04 17:03:31 Sleeping for 5 seconds  * Sleep for "5" seconds ...[PASS] 2025/08/04 17:03:36 Verifying if the cronjob tekton-resource-pruner is not present in namespace openshift-pipelines 2025/08/04 17:03:41 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2025/08/04 17:03:41 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines  * Assert if cronjob with prefix "tekton-resource-pruner" is "not present" in target namespace ...[PASS] 2025/08/04 17:03:48 output: project.project.openshift.io "releasetest-qlht4" deleted 2025/08/04 17:03:48 output: tektonconfig.operator.tekton.dev/config patched Transformed SuiteResult to report structure Successfully generated html-report to => /logs/artifacts/html-report/2025-08-04_17.03.48/index.html Done generating HTML report using theme from /tmp/plugins/html-report/4.3.3/themes/default Successfully generated xml-report to => /logs/artifacts/xml-report/2025-08-04 17.03.48 Sending kill message to Html Report plugin. Sending kill message to Xml Report plugin. Sending kill message to runner. ok command-line-arguments 929.371s Runner with PID:28202 has exited Specifications: 1 executed 1 passed 0 failed 0 skipped Scenarios: 5 executed 5 passed 0 failed 0 skipped Total time taken: 15m29.287s Updates are available. Run `gauge update -c` for more info. gauge run specs/operator/rbac.spec log-level : [debug] tags : [sanity] verbose : [true] env will be loaded from default directory 'env' 'gauge_environment' set to 'default' Created gauge_screenshots_dir at /tmp/release-tests/.gauge/screenshots Plugin go is already installed. Plugin html-report is already installed. Plugin xml-report is already installed. Parsing started. Started concepts parsing. 14 concepts parsing completed. Started specifications parsing. 1 specifications parsing completed. Applying tags filter: sanity The following specifications satisfy filter criteria: specs/operator/rbac.spec Parsing completed. Starting go runner Checking updates... Downloading https://downloads.gauge.org/plugin/go?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Downloading https://downloads.gauge.org/plugin/html-report?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Downloading https://downloads.gauge.org/plugin/xml-report?l=go&p=go,html-report,xml-report&o=linux&a=amd64 Established connection to runner. Validation started. Validation completed. Run started Starting Html Report plugin Setting MaxRecvMsgSize = 1024 MB Attempting to connect to grpc server at port: 45999 Successfully made the connection with plugin with port: 45999 Starting Xml Report plugin Attempting to connect to grpc server at port: 35427 Successfully made the connection with plugin with port: 35427 Initialising suite data store. # Verify RBAC Resources  ## Disable RBAC resource creation: PIPELINES-11-TC01 2025/08/04 17:03:53 output: Now using project "releasetest-hk5m8" on server "https://api.ci-op-1wl1tlmv-ee0eb.cspilp.interop.ccitredhat.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname 2025/08/04 17:03:58 Waiting for operator to be up and running.... 2025/08/04 17:03:58 Operator is up  * Validate Operator should be installed ...[PASS] 2025/08/04 17:03:58 enable auto creation of RBAC resources 2025/08/04 17:03:58 output: tektonconfig.operator.tekton.dev/config patched  * Update TektonConfig CR to use param with name createRbacResource and value "true" to "enable" auto creation of RBAC resources ...[PASS] 2025/08/04 17:03:58 Verifying that TektonConfig status is "installed" 2025/08/04 17:04:03 Verifying that service account pipeline exists 2025/08/04 17:04:08 Verifying that cluster role pipelines-scc-clusterrole exists 2025/08/04 17:04:13 Verifying that config map config-service-cabundle exists 2025/08/04 17:04:18 Verifying that config map config-trusted-cabundle exists 2025/08/04 17:04:23 Verifying that role binding openshift-pipelines-edit exists 2025/08/04 17:04:28 Verifying that role binding pipelines-scc-rolebinding exists 2025/08/04 17:04:33 Verifying that security context constraint pipelines-scc exists  * Verify RBAC resources are auto created successfully ...[PASS] 2025/08/04 17:04:33 disable auto creation of RBAC resources 2025/08/04 17:04:33 output: tektonconfig.operator.tekton.dev/config patched  * Update TektonConfig CR to use param with name createRbacResource and value "false" to "disable" auto creation of RBAC resources ...[PASS] 2025/08/04 17:04:38 Verifying that service account pipeline exists 2025/08/04 17:04:43 Verifying that cluster role pipelines-scc-clusterrole doesn't exist 2025/08/04 17:04:48 Verifying that config map config-service-cabundle doesn't exist 2025/08/04 17:04:53 Verifying that config map config-trusted-cabundle doesn't exist 2025/08/04 17:04:58 Verifying that role binding edit doesn't exist 2025/08/04 17:05:03 Verifying that role binding pipelines-scc-rolebinding doesn't exist 2025/08/04 17:05:08 Verifying that security context constraint pipelines-scc doesn't exist  * Verify RBAC resources disabled successfully ...[PASS] 2025/08/04 17:05:08 enable auto creation of RBAC resources 2025/08/04 17:05:08 output: tektonconfig.operator.tekton.dev/config patched  * Update TektonConfig CR to use param with name createRbacResource and value "true" to "enable" auto creation of RBAC resources ...[PASS] 2025/08/04 17:05:08 Verifying that TektonConfig status is "installed" 2025/08/04 17:05:13 Verifying that service account pipeline exists 2025/08/04 17:05:18 Verifying that cluster role pipelines-scc-clusterrole exists 2025/08/04 17:05:24 Verifying that config map config-service-cabundle exists 2025/08/04 17:05:29 Verifying that config map config-trusted-cabundle exists 2025/08/04 17:05:34 Verifying that role binding openshift-pipelines-edit exists 2025/08/04 17:05:39 Verifying that role binding pipelines-scc-rolebinding exists 2025/08/04 17:05:44 Verifying that security context constraint pipelines-scc exists  * Verify RBAC resources are auto created successfully ...[PASS] 2025/08/04 17:05:52 output: project.project.openshift.io "releasetest-hk5m8" deleted Transformed SuiteResult to report structure Successfully generated html-report to => /logs/artifacts/html-report/2025-08-04_17.05.52/index.html Done generating HTML report using theme from /tmp/plugins/html-report/4.3.3/themes/default Successfully generated xml-report to => /logs/artifacts/xml-report/2025-08-04 17.05.52 Sending kill message to Html Report plugin. Sending kill message to Xml Report plugin. Sending kill message to runner. ok command-line-arguments 119.061s Runner with PID:29821 has exited Specifications: 1 executed 1 passed 0 failed 0 skipped Scenarios: 1 executed 1 passed 0 failed 0 skipped Total time taken: 1m58.998s Updates are available. Run `gauge update -c` for more info. Rename xml files to junit_test_*.xml