WARNING: Using insecure TLS client config. Setting this option is not supported! Login successful. You have access to 70 projects, the list has been suppressed. You can list all projects with 'oc projects' Using project "default". Running olm.spec to install operator gauge run specs/olm.spec log-level : [debug] tags : [install] 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.22.1 go: downloading github.com/sirupsen/logrus v1.9.3 go: downloading github.com/spf13/cobra v1.7.0 go: downloading github.com/mattn/go-isatty v0.0.20 go: downloading gopkg.in/yaml.v2 v2.4.0 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/google/go-dap v0.11.0 go: downloading github.com/spf13/pflag v1.0.5 go: downloading github.com/hashicorp/golang-lru v1.0.2 go: downloading golang.org/x/arch v0.6.0 go: downloading go.starlark.net v0.0.0-20231101134539-556fd59b42f6 go: downloading golang.org/x/sys v0.13.0 go: downloading github.com/cilium/ebpf v0.11.0 go: downloading github.com/cpuguy83/go-md2man/v2 v2.0.2 go: downloading gopkg.in/yaml.v3 v3.0.1 go: downloading github.com/mattn/go-runewidth v0.0.13 go: downloading github.com/russross/blackfriday/v2 v2.1.0 go: downloading github.com/rivo/uniseg v0.2.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.4.0 go: downloading github.com/getgauge/common v0.0.0-20211105093448-e0aee1ccb217 go: downloading github.com/golang/protobuf v1.5.3 go: downloading github.com/dmotylev/goproperties v0.0.0-20140630191356-7cbffbaada47 go: downloading google.golang.org/protobuf v1.31.0 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.1/html-report-4.3.1-linux.x86_64.zip ....................... Installing plugin html-report 4.3.1 Successfully installed plugin 'html-report' version 4.3.1 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.1/xml-report-0.5.1-linux.x86_64.zip ........................ Installing plugin xml-report 0.5.1 Successfully installed plugin 'xml-report' version 0.5.1 Parsing started. Started concepts parsing. 14 concepts parsing completed. Started specifications parsing. 1 specifications parsing completed. Applying tags filter: install The following specifications satisfy filter criteria: specs/olm.spec Parsing completed. Starting go runner go: downloading github.com/openshift/client-go v0.0.0-20230503144108-75015d2347cb go: downloading github.com/operator-framework/operator-lifecycle-manager v0.22.0 go: downloading k8s.io/client-go v0.26.8 go: downloading github.com/tektoncd/operator v0.70.0 go: downloading github.com/tektoncd/pipeline v0.56.1 go: downloading k8s.io/apimachinery v0.26.8 go: downloading github.com/tektoncd/triggers v0.26.1 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 gotest.tools/v3 v3.5.1 go: downloading github.com/operator-framework/api v0.16.0 go: downloading github.com/pkg/errors v0.9.1 go: downloading github.com/tektoncd/cli v0.35.2 go: downloading k8s.io/api v0.26.8 go: downloading knative.dev/pkg v0.0.0-20231103161548-f5b42e8dea44 go: downloading github.com/openshift/api v0.0.0-20230503133300-8bbcb7ca7183 go: downloading github.com/prometheus/client_golang v1.18.0 go: downloading github.com/prometheus/common v0.45.0 go: downloading go.opencensus.io v0.24.0 go: downloading github.com/google/go-cmp v0.6.0 go: downloading github.com/gogo/protobuf v1.3.2 go: downloading k8s.io/klog/v2 v2.110.1 go: downloading sigs.k8s.io/structured-merge-diff/v4 v4.4.1 go: downloading github.com/imdario/mergo v0.3.16 go: downloading golang.org/x/term v0.16.0 go: downloading golang.org/x/net v0.20.0 go: downloading k8s.io/utils v0.0.0-20230726121419-3b25d923346b go: downloading github.com/google/gofuzz v1.2.0 go: downloading github.com/google/cel-go v0.19.0 go: downloading golang.org/x/exp v0.0.0-20231110203233-9a3e6036ecaa go: downloading k8s.io/kube-openapi v0.0.0-20230525220651-2546d827e515 go: downloading github.com/google/go-containerregistry v0.19.0 go: downloading github.com/json-iterator/go v1.1.12 go: downloading github.com/manifestival/manifestival v0.7.2 go: downloading github.com/openshift-pipelines/pipelines-as-code v0.24.1 go: downloading go.uber.org/zap v1.26.0 go: downloading golang.org/x/xerrors v0.0.0-20231012003039-104605ab7028 go: downloading knative.dev/eventing v0.39.0 go: downloading github.com/cloudevents/sdk-go/v2 v2.14.0 go: downloading github.com/tidwall/sjson v1.2.4 go: downloading github.com/golang/groupcache v0.0.0-20210331224755-41bb18bfe9da go: downloading github.com/google/gnostic v0.7.0 go: downloading sigs.k8s.io/json v0.0.0-20221116044647-bc3834ca7abd go: downloading github.com/go-logr/logr v1.3.0 go: downloading sigs.k8s.io/yaml v1.4.0 go: downloading golang.org/x/time v0.5.0 go: downloading github.com/davecgh/go-spew v1.1.2-0.20180830191138-d8f796af33cc go: downloading golang.org/x/oauth2 v0.16.0 go: downloading golang.org/x/sys v0.16.0 go: downloading gopkg.in/inf.v0 v0.9.1 go: downloading github.com/blang/semver/v4 v4.0.0 go: downloading google.golang.org/genproto/googleapis/api v0.0.0-20240122161410-6c6643bf1457 go: downloading google.golang.org/protobuf v1.32.0 go: downloading github.com/fatih/color v1.16.0 go: downloading github.com/jonboulle/clockwork v0.4.0 go: downloading github.com/spf13/cobra v1.8.0 go: downloading go.uber.org/multierr v1.11.0 go: downloading k8s.io/cli-runtime v0.26.13 go: downloading github.com/AlecAivazis/survey/v2 v2.3.7 go: downloading github.com/ktr0731/go-fuzzyfinder v0.8.0 go: downloading github.com/hashicorp/go-multierror v1.1.1 go: downloading github.com/emicklei/go-restful/v3 v3.11.0 go: downloading github.com/openshift/apiserver-library-go v0.0.0-20230503174907-d9b2bf6185e9 go: downloading github.com/go-openapi/swag v0.22.4 go: downloading github.com/go-openapi/jsonreference v0.20.2 go: downloading github.com/evanphx/json-patch/v5 v5.7.0 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.7.0+incompatible go: downloading google.golang.org/grpc v1.61.0 go: downloading k8s.io/apiextensions-apiserver v0.26.8 go: downloading github.com/blendle/zapdriver v1.3.1 go: downloading github.com/google/uuid v1.5.0 go: downloading golang.org/x/sync v0.6.0 go: downloading contrib.go.opencensus.io/exporter/ocagent v0.7.1-0.20200907061046-05415f1de66d go: downloading contrib.go.opencensus.io/exporter/prometheus v0.4.2 go: downloading go.uber.org/atomic v1.11.0 go: downloading github.com/tidwall/gjson v1.12.1 go: downloading github.com/opencontainers/go-digest v1.0.0 go: downloading github.com/google/gnostic-models v0.6.9-0.20230804172637-c7be7c783f49 go: downloading golang.org/x/text v0.14.0 go: downloading github.com/stoewer/go-strcase v1.3.0 go: downloading github.com/antlr4-go/antlr/v4 v4.13.0 go: downloading github.com/hako/durafmt v0.0.0-20210608085754-5c1018a4e16b go: downloading github.com/mattn/go-colorable v0.1.13 go: downloading github.com/kballard/go-shellquote v0.0.0-20180428030007-95032a82bc51 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.15 go: downloading github.com/nsf/termbox-go v1.1.1 go: downloading github.com/hashicorp/errwrap v1.1.0 go: downloading github.com/go-openapi/jsonpointer v0.20.0 go: downloading gomodules.xyz/jsonpatch/v2 v2.4.0 go: downloading github.com/mailru/easyjson v0.7.7 go: downloading github.com/kelseyhightower/envconfig v1.4.0 go: downloading github.com/census-instrumentation/opencensus-proto v0.4.1 go: downloading google.golang.org/api v0.157.0 go: downloading github.com/prometheus/statsd_exporter v0.25.0 go: downloading github.com/munnerz/goautoneg v0.0.0-20191010083416-a7dc8b61c822 go: downloading sigs.k8s.io/controller-runtime v0.14.6 go: downloading github.com/tidwall/match v1.1.1 go: downloading github.com/tidwall/pretty v1.2.0 go: downloading github.com/mgutz/ansi v0.0.0-20200706080929-d51e80ef957d go: downloading github.com/rivo/uniseg v0.4.4 go: downloading github.com/liggitt/tabwriter v0.0.0-20181228230101-89fcab3d43de go: downloading sigs.k8s.io/kustomize/api v0.12.1 go: downloading sigs.k8s.io/kustomize/kyaml v0.13.9 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/gdamore/encoding v1.0.0 go: downloading github.com/lucasb-eyer/go-colorful v1.2.0 go: downloading github.com/josharian/intern v1.0.0 go: downloading github.com/grpc-ecosystem/grpc-gateway/v2 v2.18.1 go: downloading github.com/prometheus/client_model v0.5.0 go: downloading github.com/beorn7/perks v1.0.1 go: downloading github.com/cespare/xxhash/v2 v2.2.0 go: downloading github.com/prometheus/procfs v0.12.0 go: downloading google.golang.org/genproto/googleapis/rpc v0.0.0-20240116215550-a9fa1716bcac go: downloading github.com/go-kit/log v0.2.1 go: downloading github.com/google/btree v1.1.2 go: downloading github.com/matttproud/golang_protobuf_extensions/v2 v2.0.0 go: downloading github.com/go-errors/errors v1.4.2 go: downloading github.com/go-logfmt/logfmt v0.6.0 go: downloading github.com/google/shlex v0.0.0-20191202100458-e7afc7fbc510 go: downloading github.com/monochromegane/go-gitignore v0.0.0-20200626010858-205db1a8cc00 go: downloading github.com/xlab/treeprint v1.2.0 go: downloading go.starlark.net v0.0.0-20200306205701-8dd3e2ee1dd5 Established connection to runner. Validation started. Validation completed. Run started Starting Html Report plugin Attempting to connect to grpc server at port: 40225 Successfully made the connection with plugin with port: 40225 Starting Xml Report plugin Attempting to connect to grpc server at port: 44949 Successfully made the connection with plugin with port: 44949 Initialising suite data store. # Olm Openshift Pipelines operator specs  ## Install openshift-pipelines operator: PIPELINES-09-TC01 2024/04/29 06:54:53 output: Now using project "releasetest-tsqwf" on server "https://api.ci-op-bfkt0dtt-c64b7.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 2024/04/29 06:54:55 output: subscription.operators.coreos.com/openshift-pipelines-operator-rh created  * Subscribe to operator ...[PASS]  * Wait for TektonConfig CR availability ...[PASS] 2024/04/29 06:55:56 output: tektonconfig.operator.tekton.dev/config patched  * Define the tekton-hub-api variable ...[PASS] 2024/04/29 06:55:56 Verify namespace "openshift-pipelines" exists  * Verify namespace "openshift-pipelines" exists ...[PASS] 2024/04/29 06:56:03 output: tektonhub.operator.tekton.dev/hub created  * Apply |S.NO|resource_dir | |----|---------------------------| |1 |testdata/hub/tektonhub.yaml| ...[PASS]  * Create secrets for Tekton Results ...[PASS] 2024/04/29 06:56:08 output: persistentvolumeclaim/tekton-logs created 2024/04/29 06:56:08 output: tektonresult.operator.tekton.dev/result created  * Apply in namespace "openshift-pipelines" |S.NO|resource_dir | |----|-----------------------------| |1 |testdata/pvc/tekton-logs.yaml| |2 |testdata/results/result.yaml | ...[PASS]  * Create Results route ...[PASS]  * Create signing-secrets for Tekton Chains ...[PASS] 2024/04/29 06:56:10 Token for authorization to the GitHub repository was not exported as a system variable  * Configure GitHub token for git resolver in TektonConfig ...[PASS] 2024/04/29 06:56:10 output: tektonconfig.operator.tekton.dev/config patched  * Configure the bundles resolver ...[PASS] 2024/04/29 06:56:10 Already enabled console plugins: ["monitoring-plugin"]  * Enable console plugin ...[PASS] 2024/04/29 06:56:16 Waiting for full availability of deployment tekton-pipelines-controller (0/1) 2024/04/29 06:56:21 Waiting for full availability of deployment tekton-pipelines-controller (0/1) 2024/04/29 06:56:26 Waiting for full availability of deployment tekton-pipelines-controller (0/1)  * Validate pipelines deployment ...[PASS]  * Validate triggers deployment ...[PASS] 2024/04/29 06:56:56 Waiting for availability of pipelines-as-code-controller deployment 2024/04/29 06:57:01 Waiting for availability of pipelines-as-code-controller deployment 2024/04/29 06:57:06 Waiting for availability of pipelines-as-code-controller deployment 2024/04/29 06:57:11 Waiting for availability of pipelines-as-code-controller deployment 2024/04/29 06:57:16 Waiting for availability of pipelines-as-code-controller deployment 2024/04/29 06:57:21 Waiting for availability of pipelines-as-code-controller deployment 2024/04/29 06:57:26 Waiting for availability of pipelines-as-code-controller deployment 2024/04/29 06:57:31 Waiting for availability of pipelines-as-code-controller deployment 2024/04/29 06:57:36 Waiting for full availability of deployment pipelines-as-code-controller (0/1) 2024/04/29 06:57:41 Waiting for full availability of deployment pipelines-as-code-controller (0/1) 2024/04/29 06:57:51 Waiting for full availability of deployment pipelines-as-code-watcher (0/1)  * Validate PAC deployment ...[PASS]  * Validate chains deployment ...[PASS]  * Validate hub deployment ...[PASS]  * Validate tkn server cli deployment ...[PASS]  * Validate console plugin deployment ...[PASS]  * Ensure that Tekton Results is ready ...[PASS]  * Verify TektonAddons Install status ...[PASS] 2024/04/29 06:58:46 Verifying that TektonConfig status is "installed" 2024/04/29 06:58:51 Verifying that service account pipeline exists 2024/04/29 06:58:56 Verifying that cluster role pipelines-scc-clusterrole exists 2024/04/29 06:59:01 Verifying that config map config-service-cabundle exists 2024/04/29 06:59:06 Verifying that config map config-trusted-cabundle exists 2024/04/29 06:59:11 Verifying that role binding openshift-pipelines-edit exists 2024/04/29 06:59:16 Verifying that role binding pipelines-scc-rolebinding exists 2024/04/29 06:59:22 Verifying that security context constraint pipelines-scc exists  * Validate RBAC ...[PASS]  * Validate quickstarts ...[PASS] 2024/04/29 06:59:22 Cronjob with schedule 0 8 * * * and with name prefix tekton-resource-pruner- is present  * Validate default auto prune cronjob in target namespace ...[PASS] 2024/04/29 06:59:22 Verifying if the installerset addon-custom-clustertask-mhkxj is in ready state 2024/04/29 06:59:22 Verifying if the installerset addon-custom-communityclustertask-d8g2s is in ready state 2024/04/29 06:59:22 Verifying if the installerset addon-custom-consolecli-vrwxp is in ready state 2024/04/29 06:59:22 Verifying if the installerset addon-custom-openshiftconsole-qkwqv is in ready state 2024/04/29 06:59:22 Verifying if the installerset addon-custom-pipelinestemplate-xbn7h is in ready state 2024/04/29 06:59:22 Verifying if the installerset addon-custom-triggersresources-xmnqk is in ready state 2024/04/29 06:59:22 Verifying if the installerset addon-versioned-clustertasks-1.14-gqvh9 is in ready state 2024/04/29 06:59:22 Verifying if the installerset chain-config-62kv2 is in ready state 2024/04/29 06:59:22 Verifying if the installerset chain-secret-hlqhm is in ready state 2024/04/29 06:59:22 Verifying if the installerset chain-v52rb is in ready state 2024/04/29 06:59:22 Verifying if the installerset console-link-hub-szbpj is in ready state 2024/04/29 06:59:22 Verifying if the installerset openshiftpipelinesascode-main-deployment-vhm4n is in ready state 2024/04/29 06:59:22 Verifying if the installerset openshiftpipelinesascode-main-static-xx2ls is in ready state 2024/04/29 06:59:22 Verifying if the installerset openshiftpipelinesascode-post-6xc5c is in ready state 2024/04/29 06:59:22 Verifying if the installerset pipeline-main-deployment-9lsdp is in ready state 2024/04/29 06:59:22 Verifying if the installerset pipeline-main-static-kvxwq is in ready state 2024/04/29 06:59:22 Verifying if the installerset pipeline-post-vz95q is in ready state 2024/04/29 06:59:22 Verifying if the installerset pipeline-pre-hmhzg is in ready state 2024/04/29 06:59:22 Verifying if the installerset result-n8cts is in ready state 2024/04/29 06:59:22 Verifying if the installerset result-post-dvl5h is in ready state 2024/04/29 06:59:22 Verifying if the installerset result-pre-t6tws is in ready state 2024/04/29 06:59:22 Verifying if the installerset rhosp-rbac-mc72q is in ready state 2024/04/29 06:59:22 Verifying if the installerset tekton-config-console-plugin-manifests-m7wsp is in ready state 2024/04/29 06:59:22 Verifying if the installerset tekton-hub-api-44xmr is in ready state 2024/04/29 06:59:22 Verifying if the installerset tekton-hub-db-cmkg6 is in ready state 2024/04/29 06:59:22 Verifying if the installerset tekton-hub-db-migration-6qmwz is in ready state 2024/04/29 06:59:22 Verifying if the installerset tekton-hub-ui-jdmqc is in ready state 2024/04/29 06:59:22 Verifying if the installerset tektoncd-pruner-qtmnq is in ready state 2024/04/29 06:59:22 Verifying if the installerset trigger-main-deployment-5phqh is in ready state 2024/04/29 06:59:22 Verifying if the installerset trigger-main-static-bj27m is in ready state 2024/04/29 06:59:22 Verifying if the installerset validating-mutating-webhook-xj2fw is in ready state 2024/04/29 06:59:22 All the installersets are in ready state  * Validate tektoninstallersets status ...[PASS] 2024/04/29 06:59:22 Verifying if the installerset with prefix addon-custom-clustertask is present 2024/04/29 06:59:22 Installerset with prefix addon-custom-clustertask is present 2024/04/29 06:59:22 Verifying if the installerset with prefix addon-custom-communityclustertask is present 2024/04/29 06:59:22 Installerset with prefix addon-custom-communityclustertask is present 2024/04/29 06:59:22 Verifying if the installerset with prefix addon-custom-consolecli is present 2024/04/29 06:59:22 Installerset with prefix addon-custom-consolecli is present 2024/04/29 06:59:22 Verifying if the installerset with prefix addon-custom-openshiftconsole is present 2024/04/29 06:59:22 Installerset with prefix addon-custom-openshiftconsole is present 2024/04/29 06:59:22 Verifying if the installerset with prefix addon-custom-pipelinestemplate is present 2024/04/29 06:59:22 Installerset with prefix addon-custom-pipelinestemplate is present 2024/04/29 06:59:22 Verifying if the installerset with prefix addon-custom-triggersresources is present 2024/04/29 06:59:22 Installerset with prefix addon-custom-triggersresources is present 2024/04/29 06:59:22 Verifying if the installerset with prefix addon-versioned-clustertasks is present 2024/04/29 06:59:22 Installerset with prefix addon-versioned-clustertasks is present 2024/04/29 06:59:22 Verifying if the installerset with prefix chain is present 2024/04/29 06:59:22 Installerset with prefix chain is present 2024/04/29 06:59:22 Verifying if the installerset with prefix chain-secret is present 2024/04/29 06:59:22 Installerset with prefix chain-secret is present 2024/04/29 06:59:22 Verifying if the installerset with prefix console-link-hub is present 2024/04/29 06:59:22 Installerset with prefix console-link-hub is present 2024/04/29 06:59:22 Verifying if the installerset with prefix openshiftpipelinesascode-main-deployment is present 2024/04/29 06:59:22 Installerset with prefix openshiftpipelinesascode-main-deployment is present 2024/04/29 06:59:22 Verifying if the installerset with prefix openshiftpipelinesascode-main-static is present 2024/04/29 06:59:22 Installerset with prefix openshiftpipelinesascode-main-static is present 2024/04/29 06:59:22 Verifying if the installerset with prefix openshiftpipelinesascode-post is present 2024/04/29 06:59:22 Installerset with prefix openshiftpipelinesascode-post is present 2024/04/29 06:59:22 Verifying if the installerset with prefix pipeline-main-deployment is present 2024/04/29 06:59:22 Installerset with prefix pipeline-main-deployment is present 2024/04/29 06:59:22 Verifying if the installerset with prefix pipeline-main-static is present 2024/04/29 06:59:22 Installerset with prefix pipeline-main-static is present 2024/04/29 06:59:22 Verifying if the installerset with prefix pipeline-post is present 2024/04/29 06:59:22 Installerset with prefix pipeline-post is present 2024/04/29 06:59:22 Verifying if the installerset with prefix pipeline-pre is present 2024/04/29 06:59:22 Installerset with prefix pipeline-pre is present 2024/04/29 06:59:22 Verifying if the installerset with prefix rhosp-rbac is present 2024/04/29 06:59:22 Installerset with prefix rhosp-rbac is present 2024/04/29 06:59:22 Verifying if the installerset with prefix tekton-hub-api is present 2024/04/29 06:59:22 Installerset with prefix tekton-hub-api is present 2024/04/29 06:59:22 Verifying if the installerset with prefix tekton-hub-db is present 2024/04/29 06:59:22 Installerset with prefix tekton-hub-db is present 2024/04/29 06:59:22 Verifying if the installerset with prefix tekton-hub-db-migration is present 2024/04/29 06:59:22 Installerset with prefix tekton-hub-db-migration is present 2024/04/29 06:59:22 Verifying if the installerset with prefix tekton-hub-ui is present 2024/04/29 06:59:22 Installerset with prefix tekton-hub-ui is present 2024/04/29 06:59:22 Verifying if the installerset with prefix tektoncd-pruner is present 2024/04/29 06:59:22 Installerset with prefix tektoncd-pruner is present 2024/04/29 06:59:22 Verifying if the installerset with prefix trigger-main-deployment is present 2024/04/29 06:59:22 Installerset with prefix trigger-main-deployment is present 2024/04/29 06:59:22 Verifying if the installerset with prefix trigger-main-static is present 2024/04/29 06:59:22 Installerset with prefix trigger-main-static is present 2024/04/29 06:59:22 Verifying if the installerset with prefix validating-mutating-webhook is present 2024/04/29 06:59:22 Installerset with prefix validating-mutating-webhook is present 2024/04/29 06:59:22 Verifying if the installerset with prefix tekton-config-console-plugin-manifests is present 2024/04/29 06:59:22 Installerset with prefix tekton-config-console-plugin-manifests is present  * Validate tektoninstallersets names ...[PASS] 2024/04/29 06:59:30 output: project.project.openshift.io "releasetest-tsqwf" deleted Transformed SuiteResult to report structure Successfully generated html-report to => /logs/artifacts/html-report/2024-04-29_06.59.30/index.html Done generating HTML report using theme from /tmp/plugins/html-report/4.3.1/themes/default Successfully generated xml-report to => /logs/artifacts/xml-report/2024-04-29 06.59.30 Sending kill message to Xml Report plugin. Sending kill message to Html Report plugin. Sending kill message to runner. ok command-line-arguments 277.644s Runner with PID:4205 has exited Specifications: 1 executed 1 passed 0 failed 0 skipped Scenarios: 1 executed 1 passed 0 failed 0 skipped Total time taken: 4m37.428s Updates are available. Run `gauge update -c` for more info. Running gauge specs gauge run specs/clustertasks/clustertask-s2i.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/clustertasks/clustertask-s2i.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: 33223 Successfully made the connection with plugin with port: 33223 Starting Xml Report plugin Attempting to connect to grpc server at port: 33685 Successfully made the connection with plugin with port: 33685 Initialising suite data store. # Verify Clustertasks E2E spec  ## S2I nodejs pipelinerun: PIPELINES-14-TC01 2024/04/29 06:59:44 output: Now using project "releasetest-zz2kj" on server "https://api.ci-op-bfkt0dtt-c64b7.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 2024/04/29 06:59:45 Waiting for operator to be up and running.... 2024/04/29 06:59:45 Waiting for config cr InstalledStatus Actual: [False] Expected: [True] 2024/04/29 06:59:50 Operator is up  * Validate Operator should be installed ...[PASS] 2024/04/29 06:59:50 Verify SA "pipeline" is created in namespace "releasetest-zz2kj"  * Verify ServiceAccount "pipeline" exist ...[PASS] 2024/04/29 06:59:51 output: imagestream.image.openshift.io/nodejs-ex-git created deploymentconfig.apps.openshift.io/nodejs-ex-git created pipeline.tekton.dev/nodejs-ex-git created pipelinerun.tekton.dev/nodejs-ex-git-pr created  * Create |S.NO|resource_dir | |----|--------------------------------------------------------| |1 |testdata/v1beta1/pipelinerun/s2i-nodejs-pipelinerun.yaml| ...[PASS] 2024/04/29 06:59:51 validating pipeline run for success state... 2024/04/29 07:02:36 pipelineRun: nodejs-ex-git-pr is successful under namespace : releasetest-zz2kj  * Verify pipelinerun |S.NO|pipeline_run_name|status |check_lable_propagation| |----|-----------------|----------|-----------------------| |1 |nodejs-ex-git-pr |successful|no | ...[PASS] 2024/04/29 07:02:51 output: project.project.openshift.io "releasetest-zz2kj" deleted  ## S2I java pipelinerun: PIPELINES-14-TC04 2024/04/29 07:02:51 output: Now using project "releasetest-754bp" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:02:51 Verify SA "pipeline" is created in namespace "releasetest-754bp"  * Verify ServiceAccount "pipeline" exist ...[PASS] 2024/04/29 07:02:56 output: pipeline.tekton.dev/s2i-java-pipeline created 2024/04/29 07:02:56 output: persistentvolumeclaim/shared-pvc created  * Create |S.NO|resource_dir | |----|----------------------------------------------------| |1 |testdata/v1beta1/clustertask/pipelines/s2i-java.yaml| |2 |testdata/pvc/pvc.yaml | ...[PASS] 2024/04/29 07:02:56 Getting imagestream from the namespace openshift  * Get tags of the imagestream "java" from namespace "openshift" and store to variable "java-tags" ...[PASS] 2024/04/29 07:02:57 Starting pipeline s2i-java-pipeline with param VERSION=11 2024/04/29 07:02:57 Pipelinerun s2i-java-pipeline-run-ph9g9 started 2024/04/29 07:02:57 validating pipeline run for success state... 2024/04/29 07:04:52 pipelineRun: s2i-java-pipeline-run-ph9g9 is successful under namespace : releasetest-754bp 2024/04/29 07:04:52 Starting pipeline s2i-java-pipeline with param VERSION=8 2024/04/29 07:04:52 Pipelinerun s2i-java-pipeline-run-x6nx8 started 2024/04/29 07:04:52 validating pipeline run for success state... 2024/04/29 07:06:57 pipelineRun: s2i-java-pipeline-run-x6nx8 is successful under namespace : releasetest-754bp 2024/04/29 07:06:57 Starting pipeline s2i-java-pipeline with param VERSION=openjdk-11-el7 2024/04/29 07:06:57 Pipelinerun s2i-java-pipeline-run-tpjmm started 2024/04/29 07:06:57 validating pipeline run for success state... 2024/04/29 07:08:57 pipelineRun: s2i-java-pipeline-run-tpjmm is successful under namespace : releasetest-754bp 2024/04/29 07:08:57 Starting pipeline s2i-java-pipeline with param VERSION=openjdk-11-ubi8 2024/04/29 07:08:58 Pipelinerun s2i-java-pipeline-run-kpf8t started 2024/04/29 07:08:58 validating pipeline run for success state... 2024/04/29 07:10:23 pipelineRun: s2i-java-pipeline-run-kpf8t is successful under namespace : releasetest-754bp 2024/04/29 07:10:23 Starting pipeline s2i-java-pipeline with param VERSION=openjdk-17-ubi8 2024/04/29 07:10:23 Pipelinerun s2i-java-pipeline-run-z2jr8 started 2024/04/29 07:10:23 validating pipeline run for success state... 2024/04/29 07:11:53 pipelineRun: s2i-java-pipeline-run-z2jr8 is successful under namespace : releasetest-754bp 2024/04/29 07:11:53 Starting pipeline s2i-java-pipeline with param VERSION=openjdk-8-el7 2024/04/29 07:11:53 Pipelinerun s2i-java-pipeline-run-jsw2h started 2024/04/29 07:11:53 validating pipeline run for success state... 2024/04/29 07:13:53 pipelineRun: s2i-java-pipeline-run-jsw2h is successful under namespace : releasetest-754bp 2024/04/29 07:13:53 Starting pipeline s2i-java-pipeline with param VERSION=openjdk-8-ubi8 2024/04/29 07:13:53 Pipelinerun s2i-java-pipeline-run-n6pn8 started 2024/04/29 07:13:53 validating pipeline run for success state... 2024/04/29 07:15:23 pipelineRun: s2i-java-pipeline-run-n6pn8 is successful under namespace : releasetest-754bp  * Start and verify pipeline "s2i-java-pipeline" with param "VERSION" with values stored in variable "java-tags" with workspace "name=source,claimName=shared-pvc" ...[PASS] 2024/04/29 07:15:38 output: project.project.openshift.io "releasetest-754bp" deleted Transformed SuiteResult to report structure Successfully generated html-report to => /logs/artifacts/html-report/2024-04-29_07.15.38/index.html Done generating HTML report using theme from /tmp/plugins/html-report/4.3.1/themes/default Successfully generated xml-report to => /logs/artifacts/xml-report/2024-04-29 07.15.38 Sending kill message to Html Report plugin. Sending kill message to Xml Report plugin. Sending kill message to runner. ok command-line-arguments 954.835s Runner with PID:24896 has exited Specifications: 1 executed 1 passed 0 failed 0 skipped Scenarios: 2 executed 2 passed 0 failed 0 skipped Total time taken: 15m54.749s Updates are available. Run `gauge update -c` for more info. gauge run specs/clustertasks/clustertask.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/clustertasks/clustertask.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: 46005 Successfully made the connection with plugin with port: 46005 Starting Xml Report plugin Attempting to connect to grpc server at port: 45955 Successfully made the connection with plugin with port: 45955 Initialising suite data store. # Verify Clustertasks E2E spec  ## buildah pipelinerun: PIPELINES-16-TC01 2024/04/29 07:15:43 output: Now using project "releasetest-sjb5g" on server "https://api.ci-op-bfkt0dtt-c64b7.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 2024/04/29 07:15:43 Waiting for operator to be up and running.... 2024/04/29 07:15:43 Operator is up  * Validate Operator should be installed ...[PASS] 2024/04/29 07:15:43 Verify SA "pipeline" is created in namespace "releasetest-sjb5g"  * Verify ServiceAccount "pipeline" exist ...[PASS] 2024/04/29 07:15:43 output: pipeline.tekton.dev/buildah-pipeline created 2024/04/29 07:15:44 output: persistentvolumeclaim/shared-pvc created 2024/04/29 07:15:44 output: pipelinerun.tekton.dev/buildah-run created  * Create |S.NO|resource_dir | |----|-------------------------------------------------| |1 |testdata/v1/clustertask/pipelines/buildah.yaml | |2 |testdata/pvc/pvc.yaml | |3 |testdata/v1/clustertask/pipelineruns/buildah.yaml| ...[PASS] 2024/04/29 07:15:44 validating pipeline run for success state... 2024/04/29 07:16:29 pipelineRun: buildah-run is successful under namespace : releasetest-sjb5g  * Verify pipelinerun |S.NO|pipeline_run_name|status |check_label_propagation| |----|-----------------|----------|-----------------------| |1 |buildah-run |successful|no | ...[PASS] 2024/04/29 07:16:42 output: project.project.openshift.io "releasetest-sjb5g" deleted  ## git-clone read private repo taskrun PIPELINES-16-TC12 2024/04/29 07:16:43 output: Now using project "releasetest-7z6g9" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:16:43 Verify SA "pipeline" is created in namespace "releasetest-7z6g9"  * Verify ServiceAccount "pipeline" exist ...[PASS] 2024/04/29 07:16:48 output: pipeline.tekton.dev/git-clone-read-private-pipeline created 2024/04/29 07:16:48 output: persistentvolumeclaim/shared-pvc created 2024/04/29 07:16:48 output: secret/ssh-key created  * Create |S.NO|resource_dir | |----|-------------------------------------------------------------| |1 |testdata/v1/clustertask/pipelines/git-clone-read-private.yaml| |2 |testdata/pvc/pvc.yaml | |3 |testdata/v1/clustertask/secrets/ssh-key.yaml | ...[PASS] 2024/04/29 07:16:48 output:  * Link secret "ssh-key" to service account "pipeline" ...[PASS] 2024/04/29 07:16:49 output: pipelinerun.tekton.dev/git-clone-read-private-pipeline-run created  * Create |S.NO|resource_dir | |----|----------------------------------------------------------------| |1 |testdata/v1/clustertask/pipelineruns/git-clone-read-private.yaml| ...[PASS] 2024/04/29 07:16:49 validating pipeline run for success state... 2024/04/29 07:16:59 pipelineRun: git-clone-read-private-pipeline-run is successful under namespace : releasetest-7z6g9  * Verify pipelinerun |S.NO|pipeline_run_name |status |check_label_propagation| |----|-----------------------------------|----------|-----------------------| |1 |git-clone-read-private-pipeline-run|successful|no | ...[PASS] 2024/04/29 07:17:12 output: project.project.openshift.io "releasetest-7z6g9" deleted Transformed SuiteResult to report structure Successfully generated html-report to => /logs/artifacts/html-report/2024-04-29_07.17.12/index.html Done generating HTML report using theme from /tmp/plugins/html-report/4.3.1/themes/default Successfully generated xml-report to => /logs/artifacts/xml-report/2024-04-29 07.17.12 Sending kill message to Html Report plugin. Sending kill message to Xml Report plugin. Sending kill message to runner. ok command-line-arguments 89.349s Runner with PID:25647 has exited Specifications: 1 executed 1 passed 0 failed 0 skipped Scenarios: 2 executed 2 passed 0 failed 0 skipped Total time taken: 1m29.27s Updates are available. Run `gauge update -c` for more info. 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 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. 6 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/hub-resolvers.spec specs/pipelines/run.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: 38059 Successfully made the connection with plugin with port: 38059 Starting Xml Report plugin Attempting to connect to grpc server at port: 39561 Successfully made the connection with plugin with port: 39561 Initialising suite data store. # Bundles resolver spec  ## Test the functionality of bundles resolver with parameter: PIPELINES-25-TC02 2024/04/29 07:17:18 output: Now using project "releasetest-tnc4q" on server "https://api.ci-op-bfkt0dtt-c64b7.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 2024/04/29 07:17:18 Waiting for operator to be up and running.... 2024/04/29 07:17:19 Operator is up  * Validate Operator should be installed ...[PASS] 2024/04/29 07:17:19 Verify SA "pipeline" is created in namespace "releasetest-tnc4q"  * Verify ServiceAccount "pipeline" exist ...[PASS] 2024/04/29 07:17:19 output: pipelinerun.tekton.dev/bundles-resolver-pipelinerun-param created  * Create |S.NO|resource_dir | |----|-----------------------------------------------------------------------| |1 |testdata/resolvers/pipelineruns/bundles-resolver-pipelinerun-param.yaml| ...[PASS] 2024/04/29 07:17:19 validating pipeline run for success state... 2024/04/29 07:17:39 pipelineRun: bundles-resolver-pipelinerun-param is successful under namespace : releasetest-tnc4q  * Verify pipelinerun |S.NO|pipeline_run_name |status |check_label_propagation| |----|----------------------------------|----------|-----------------------| |1 |bundles-resolver-pipelinerun-param|successful|no | ...[PASS] 2024/04/29 07:17:52 output: project.project.openshift.io "releasetest-tnc4q" deleted # Cluster resolvers spec  ## Checking the functionality of cluster resolvers#1: PIPELINES-23-TC01 2024/04/29 07:17:53 output: Now using project "releasetest-6cbfx" on server "https://api.ci-op-bfkt0dtt-c64b7.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 2024/04/29 07:17:53 Check if project releasetest-tasks already exists 2024/04/29 07:17:53 Creating project releasetest-tasks 2024/04/29 07:17:53 output: Now using project "releasetest-tasks" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:17:54 output: task.tekton.dev/resolver-task2 created  * Create |S.NO|resource_dir | |----|--------------------------------------------| |1 |testdata/resolvers/tasks/resolver-task2.yaml| ...[PASS] 2024/04/29 07:17:54 Check if project releasetest-pipelines already exists 2024/04/29 07:17:54 Creating project releasetest-pipelines 2024/04/29 07:17:54 output: Now using project "releasetest-pipelines" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:17:54 output: pipeline.tekton.dev/resolver-pipeline created  * Create |S.NO|resource_dir | |----|---------------------------------------------------| |1 |testdata/resolvers/pipelines/resolver-pipeline.yaml| ...[PASS] 2024/04/29 07:17:54 Check if project releasetest-pipelineruns already exists 2024/04/29 07:17:54 Creating project releasetest-pipelineruns 2024/04/29 07:17:55 output: Now using project "releasetest-pipelineruns" on server "https://api.ci-op-bfkt0dtt-c64b7.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-pipelineruns" ...[PASS] 2024/04/29 07:17:55 Verify SA "pipeline" is created in namespace "releasetest-pipelineruns"  * Verify ServiceAccount "pipeline" exist ...[PASS] 2024/04/29 07:18:00 output: pipelinerun.tekton.dev/resolver-pipelinerun created  * Create |S.NO|resource_dir | |----|---------------------------------------------------------| |1 |testdata/resolvers/pipelineruns/resolver-pipelinerun.yaml| ...[PASS] 2024/04/29 07:18:00 validating pipeline run for success state... 2024/04/29 07:18:25 pipelineRun: resolver-pipelinerun is successful under namespace : releasetest-pipelineruns  * Verify pipelinerun |S.NO|pipeline_run_name |status |check_label_propagation| |----|--------------------|----------|-----------------------| |1 |resolver-pipelinerun|successful|no | ...[PASS] 2024/04/29 07:18:25 Deleting project releasetest-tasks 2024/04/29 07:18:32 output: project.project.openshift.io "releasetest-tasks" deleted  * Delete project "releasetest-tasks" ...[PASS] 2024/04/29 07:18:32 Deleting project releasetest-pipelines 2024/04/29 07:18:40 output: project.project.openshift.io "releasetest-pipelines" deleted  * Delete project "releasetest-pipelines" ...[PASS] 2024/04/29 07:18:40 Deleting project releasetest-pipelineruns 2024/04/29 07:18:53 output: project.project.openshift.io "releasetest-pipelineruns" deleted  * Delete project "releasetest-pipelineruns" ...[PASS] 2024/04/29 07:19:00 output: project.project.openshift.io "releasetest-6cbfx" deleted # Verify Pipeline Failures  ## Run Pipeline with a non-existent ServiceAccount: PIPELINES-02-TC01 2024/04/29 07:19:00 output: Now using project "releasetest-pz7ql" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:19:00 Verify SA "foobar" is absent in namespace "releasetest-pz7ql"  * Verify ServiceAccount "foobar" does not exist ...[PASS] 2024/04/29 07:19:01 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] 2024/04/29 07:19:01 validating pipeline run for failure state... 2024/04/29 07:19:01 Waiting for PipelineRun in namespace releasetest-pz7ql to fail  * Verify pipelinerun |S.NO|pipeline_run_name |status |check_label_propagation| |----|----------------------|-------|-----------------------| |1 |output-pipeline-run-vb|Failure|no | ...[PASS] 2024/04/29 07:19:19 output: project.project.openshift.io "releasetest-pz7ql" deleted # Git resolvers spec  ## Test the functionality of git resolvers: PIPELINES-24-TC01 2024/04/29 07:19:19 output: Now using project "releasetest-ztngr" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:19:19 Verify SA "pipeline" is created in namespace "releasetest-ztngr"  * Verify ServiceAccount "pipeline" exist ...[PASS] 2024/04/29 07:19:25 output: pipelinerun.tekton.dev/git-resolver-pipelinerun created  * Create |S.NO|resource_dir | |----|-------------------------------------------------------------| |1 |testdata/resolvers/pipelineruns/git-resolver-pipelinerun.yaml| ...[PASS] 2024/04/29 07:19:25 validating pipeline run for success state... 2024/04/29 07:19:35 pipelineRun: git-resolver-pipelinerun is successful under namespace : releasetest-ztngr  * Verify pipelinerun |S.NO|pipeline_run_name |status |check_label_propagation| |----|------------------------|----------|-----------------------| |1 |git-resolver-pipelinerun|successful|no | ...[PASS] 2024/04/29 07:19:49 output: project.project.openshift.io "releasetest-ztngr" deleted # HUB resolvers spec  ## Test the functionality of hub resolvers 2024/04/29 07:19:49 output: Now using project "releasetest-swzjq" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:19:49 Verify SA "pipeline" is created in namespace "releasetest-swzjq"  * Verify ServiceAccount "pipeline" exist ...[PASS] 2024/04/29 07:19:56 output: pipeline.tekton.dev/hub-git-cli-pipeline created 2024/04/29 07:19:58 output: persistentvolumeclaim/shared-pvc created 2024/04/29 07:19:58 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] 2024/04/29 07:19:58 validating pipeline run for success state... 2024/04/29 07:20:38 pipelineRun: hub-git-cli-run is successful under namespace : releasetest-swzjq  * Verify pipelinerun |S.NO|pipeline_run_name|status |check_label_propagation| |----|-----------------|----------|-----------------------| |1 |hub-git-cli-run |successful|no | ...[PASS] 2024/04/29 07:20:52 output: project.project.openshift.io "releasetest-swzjq" deleted # Verify Pipeline E2E spec  ## Pipelinerun Timeout failure Test: PIPELINES-03-TC04 2024/04/29 07:20:52 output: Now using project "releasetest-cgxmd" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:20:52 Verify SA "pipeline" is created in namespace "releasetest-cgxmd"  * Verify ServiceAccount "pipeline" exist ...[PASS] 2024/04/29 07:20:58 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] 2024/04/29 07:20:58 validating pipeline run timeout... 2024/04/29 07:20:58 Waiting for Pipelinerun pear in namespace releasetest-cgxmd to be started 2024/04/29 07:21:03 Waiting for TaskRuns from PipelineRun pear in namespace releasetest-cgxmd to be running 2024/04/29 07:21:03 Waiting for PipelineRun pear in namespace releasetest-cgxmd to be timed out 2024/04/29 07:21:08 Waiting for TaskRuns from PipelineRun pear in namespace releasetest-cgxmd to be cancelled  * Verify pipelinerun |S.NO|pipeline_run_name|status |check_label_propagation| |----|-----------------|-------|-----------------------| |1 |pear |timeout|no | ...[PASS] 2024/04/29 07:21:17 output: project.project.openshift.io "releasetest-cgxmd" deleted  ## Configure execution results at the Task level Test: PIPELINES-03-TC05 2024/04/29 07:21:17 output: Now using project "releasetest-482v7" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:21:17 Verify SA "pipeline" is created in namespace "releasetest-482v7"  * Verify ServiceAccount "pipeline" exist ...[PASS] 2024/04/29 07:21:22 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] 2024/04/29 07:21:22 validating pipeline run for success state... 2024/04/29 07:21:32 pipelineRun: task-level-results is successful under namespace : releasetest-482v7  * Verify pipelinerun |S.NO|pipeline_run_name |status |check_label_propagation| |----|------------------|----------|-----------------------| |1 |task-level-results|successful|no | ...[PASS] 2024/04/29 07:21:46 output: project.project.openshift.io "releasetest-482v7" deleted  ## Cancel pipelinerun Test: PIPELINES-03-TC06 2024/04/29 07:21:46 output: Now using project "releasetest-snf5c" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:21:46 Verify SA "pipeline" is created in namespace "releasetest-snf5c"  * Verify ServiceAccount "pipeline" exist ...[PASS] 2024/04/29 07:21:52 output: persistentvolumeclaim/shared-pvc created 2024/04/29 07:21:52 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] 2024/04/29 07:21:52 validating pipeline run timeout... 2024/04/29 07:21:52 Waiting for Pipelinerun output-pipeline-run-v1b1 in namespace releasetest-snf5c to be started 2024/04/29 07:21:57 Canceling pipeline run: PipelineRun cancelled: output-pipeline-run-v1b1 2024/04/29 07:22:02 Waiting for TaskRuns in PipelineRun output-pipeline-run-v1b1 in namespace releasetest-snf5c to be cancelled  * Verify pipelinerun |S.NO|pipeline_run_name |status |check_label_propagation| |----|------------------------|---------|-----------------------| |1 |output-pipeline-run-v1b1|cancelled|no | ...[PASS] 2024/04/29 07:22:16 output: project.project.openshift.io "releasetest-snf5c" deleted  ## Pipelinerun with large result: PIPELINES-03-TC08 2024/04/29 07:22:16 output: Now using project "releasetest-qv6d6" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:22:16 Verify SA "pipeline" is created in namespace "releasetest-qv6d6"  * Verify ServiceAccount "pipeline" exist ...[PASS] 2024/04/29 07:22:21 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] 2024/04/29 07:22:21 validating pipeline run for success state... 2024/04/29 07:22:36 pipelineRun: result-test-run is successful under namespace : releasetest-qv6d6  * Verify pipelinerun |S.NO|pipeline_run_name|status |check_label_propagation| |----|-----------------|----------|-----------------------| |1 |result-test-run |successful|no | ...[PASS] 2024/04/29 07:22:50 output: project.project.openshift.io "releasetest-qv6d6" deleted Transformed SuiteResult to report structure Successfully generated html-report to => /logs/artifacts/html-report/2024-04-29_07.22.50/index.html Done generating HTML report using theme from /tmp/plugins/html-report/4.3.1/themes/default Successfully generated xml-report to => /logs/artifacts/xml-report/2024-04-29 07.22.51 Sending kill message to Html Report plugin. Sending kill message to Xml Report plugin. Sending kill message to runner. ok command-line-arguments 332.768s Runner with PID:26371 has exited Specifications: 6 executed 6 passed 0 failed 0 skipped Scenarios: 9 executed 9 passed 0 failed 0 skipped Total time taken: 5m32.662s 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 xml-report is already installed. Plugin go is already installed. Plugin html-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 Setting MaxRecvMsgSize = 1024 MB Attempting to connect to grpc server at port: 35207 Successfully made the connection with plugin with port: 35207 Starting Xml Report plugin Attempting to connect to grpc server at port: 34625 Successfully made the connection with plugin with port: 34625 Initialising suite data store. # Verify Triggers with cronjob  ## Create Triggers using k8s cronJob: PIPELINES-04-TC01 2024/04/29 07:22:55 output: Now using project "releasetest-2pr5s" on server "https://api.ci-op-bfkt0dtt-c64b7.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 2024/04/29 07:22:55 Waiting for operator to be up and running.... 2024/04/29 07:22:55 Operator is up  * Validate Operator should be installed ...[PASS] 2024/04/29 07:22:55 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 2024/04/29 07:22:56 output: triggerbinding.triggers.tekton.dev/cron-binding created 2024/04/29 07:22:56 output: triggertemplate.triggers.tekton.dev/pipeline-template created 2024/04/29 07:22:56 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] 2024/04/29 07:22:56 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[] Annotations:map[]} AddressStatus:{Address: Addresses:[]} Configuration:{GeneratedResourceName:}} 2024/04/29 07:23:01 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:False Severity: LastTransitionTime:{Inner:2024-04-29 07:22:56 +0000 UTC} Reason:MinimumReplicasUnavailable Message:Deployment does not have minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:22:56 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:22:56 +0000 UTC} Reason:ReplicaSetUpdated Message:ReplicaSet "el-cron-listener-54895df546" is progressing.} {Type:Ready Status:False Severity: LastTransitionTime:{Inner:2024-04-29 07:22:56 +0000 UTC} Reason: Message:Condition Available has status: False with message: Deployment does not have minimum availability.} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:22:56 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc00074cc00 Addresses:[]} Configuration:{GeneratedResourceName:el-cron-listener}} 2024/04/29 07:23:06 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:23:02 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:23:02 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:23:02 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-cron-listener-54895df546" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:23:02 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:23:02 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc0004d6810 Addresses:[]} Configuration:{GeneratedResourceName:el-cron-listener}} 2024/04/29 07:23:06 sinkpod name: el-cron-listener-54895df546-kbtbl 2024/04/29 07:23:07 Route url: 'http://el-cron-listener-releasetest-2pr5s.apps.ci-op-bfkt0dtt-c64b7.cspilp.interop.ccitredhat.com'  * Expose Event listener "cron-listener" ...[PASS] 2024/04/29 07:23:12 Verify that image stream "golang" exists in namespace "openshift"  * Verify that image stream "golang" exists ...[PASS] 2024/04/29 07:23:12 Cronjob: hello created in namespace: releasetest-2pr5s  * Create cron job with schedule "*/1 * * * *" ...[PASS] 2024/04/29 07:24:01 pipeline run : simple-pipeline-run-xqtmz 2024/04/29 07:25:01 pipeline run : simple-pipeline-run-bbj6q 2024/04/29 07:26:01 pipeline run : simple-pipeline-run-zpzj2 2024/04/29 07:27:01 pipeline run : simple-pipeline-run-mj2vs 2024/04/29 07:28:01 pipeline run : simple-pipeline-run-bmgjr  * Watch for pipelinerun resources ...[PASS]  * Delete cron job ...[PASS]  * Assert no new pipelineruns created ...[PASS] 2024/04/29 07:29:12 Deleted EventListener 2024/04/29 07:29:12 EventListener's Deployment was deleted 2024/04/29 07:29:12 EventListener's Service was deleted 2024/04/29 07:29:12 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2024/04/29 07:29:27 output: project.project.openshift.io "releasetest-2pr5s" deleted # Verify eventlisteners spec  ## Create Eventlistener embedded TriggersBindings specs: PIPELINES-05-TC08 2024/04/29 07:29:27 output: Now using project "releasetest-tvgcx" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:29:28 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 2024/04/29 07:29:28 output: triggerbinding.triggers.tekton.dev/pipeline-binding created 2024/04/29 07:29:28 output: triggertemplate.triggers.tekton.dev/pipeline-template created 2024/04/29 07:29:28 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] 2024/04/29 07:29:28 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[] Annotations:map[]} AddressStatus:{Address: Addresses:[]} Configuration:{GeneratedResourceName:}} 2024/04/29 07:29:33 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:29:30 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:29:30 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:29:30 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-listener-embed-binding-74f56c6bf7" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:29:30 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:29:30 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000630360 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-embed-binding}} 2024/04/29 07:29:33 sinkpod name: el-listener-embed-binding-74f56c6bf7-x4xc5 2024/04/29 07:29:34 Route url: 'http://el-listener-embed-binding-releasetest-tvgcx.apps.ci-op-bfkt0dtt-c64b7.cspilp.interop.ccitredhat.com'  * Expose Event listener "listener-embed-binding" ...[PASS] 2024/04/29 07:29:39 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] 2024/04/29 07:29:39 validating pipeline run for success state... 2024/04/29 07:29:54 pipelineRun: simple-pipeline-run is successful under namespace : releasetest-tvgcx  * Verify pipelinerun |S.NO|pipeline_run_name |status |check_label_propagation| |----|-------------------|----------|-----------------------| |1 |simple-pipeline-run|successful|no | ...[PASS] 2024/04/29 07:29:54 Deleted EventListener 2024/04/29 07:29:59 EventListener's Deployment was deleted 2024/04/29 07:29:59 EventListener's Service was deleted 2024/04/29 07:29:59 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2024/04/29 07:30:14 output: project.project.openshift.io "releasetest-tvgcx" deleted  ## Create embedded TriggersTemplate: PIPELINES-05-TC09 2024/04/29 07:30:15 output: Now using project "releasetest-6drm5" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:30:15 output: triggerbinding.triggers.tekton.dev/pipeline-binding created 2024/04/29 07:30:15 output: triggertemplate.triggers.tekton.dev/pipeline-template created 2024/04/29 07:30:15 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] 2024/04/29 07:30:15 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[] Annotations:map[]} AddressStatus:{Address: Addresses:[]} Configuration:{GeneratedResourceName:}} 2024/04/29 07:30:20 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:30:16 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:30:16 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:30:16 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-listener-embed-binding-6df76847df" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:30:16 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:30:16 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000c7e600 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-embed-binding}} 2024/04/29 07:30:20 sinkpod name: el-listener-embed-binding-6df76847df-488dw 2024/04/29 07:30:20 Route url: 'http://el-listener-embed-binding-releasetest-6drm5.apps.ci-op-bfkt0dtt-c64b7.cspilp.interop.ccitredhat.com'  * Expose Event listener "listener-embed-binding" ...[PASS] 2024/04/29 07:30:25 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] 2024/04/29 07:30:26 validating pipeline run for success state... 2024/04/29 07:30:31 pipelineRun: pipelinerun-with-taskspec-to-echo-message is successful under namespace : releasetest-6drm5  * Verify pipelinerun |S.NO|pipeline_run_name |status |check_label_propagation| |----|-----------------------------------------|----------|-----------------------| |1 |pipelinerun-with-taskspec-to-echo-message|successful|no | ...[PASS] 2024/04/29 07:30:31 Deleted EventListener 2024/04/29 07:30:36 EventListener's Deployment was deleted 2024/04/29 07:30:36 EventListener's Service was deleted 2024/04/29 07:30:36 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2024/04/29 07:30:51 output: project.project.openshift.io "releasetest-6drm5" deleted  ## Verify Github push event with Embbeded TriggerTemplate using Github-CTB: PIPELINES-05-TC12 2024/04/29 07:30:51 output: Now using project "releasetest-ngtc9" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:30:51 output: triggertemplate.triggers.tekton.dev/pipeline-template-git-push created 2024/04/29 07:30:51 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] 2024/04/29 07:30:51 Verify SA "pipeline" is created in namespace "releasetest-ngtc9"  * Verify ServiceAccount "pipeline" exist ...[PASS] 2024/04/29 07:30:52 output: secret/github-secret created 2024/04/29 07:30:52 output:  * Create & Link secret "github-secret" to service account "pipeline" ...[PASS] 2024/04/29 07:30:52 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:False Severity: LastTransitionTime:{Inner:2024-04-29 07:30:52 +0000 UTC} Reason:MinimumReplicasUnavailable Message:Deployment does not have minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:30:52 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:30:52 +0000 UTC} Reason:ReplicaSetUpdated Message:ReplicaSet "el-listener-ctb-github-push-78ffcb9c6" is progressing.} {Type:Ready Status:False Severity: LastTransitionTime:{Inner:2024-04-29 07:30:52 +0000 UTC} Reason: Message:Condition Available has status: False with message: Deployment does not have minimum availability.} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:30:52 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000cffcb0 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-ctb-github-push}} 2024/04/29 07:30:57 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:30:53 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:30:53 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:30:53 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-listener-ctb-github-push-78ffcb9c6" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:30:53 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:30:53 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc0007d9890 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-ctb-github-push}} 2024/04/29 07:30:57 sinkpod name: el-listener-ctb-github-push-78ffcb9c6-k6f7r 2024/04/29 07:30:57 Route url: 'http://el-listener-ctb-github-push-releasetest-ngtc9.apps.ci-op-bfkt0dtt-c64b7.cspilp.interop.ccitredhat.com'  * Expose Event listener "listener-ctb-github-push" ...[PASS] 2024/04/29 07:31:02 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] 2024/04/29 07:31:02 validating pipeline run for success state... 2024/04/29 07:31:08 pipelineRun: pipelinerun-git-push-ctb is successful under namespace : releasetest-ngtc9  * Verify pipelinerun |S.NO|pipeline_run_name |status |check_label_propagation| |----|------------------------|----------|-----------------------| |1 |pipelinerun-git-push-ctb|successful|no | ...[PASS] 2024/04/29 07:31:08 Deleted EventListener 2024/04/29 07:31:13 EventListener's Deployment was deleted 2024/04/29 07:31:13 EventListener's Service was deleted 2024/04/29 07:31:13 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2024/04/29 07:31:28 output: project.project.openshift.io "releasetest-ngtc9" deleted  ## Verify Github pull_request event with Embbeded TriggerTemplate using Github-CTB: PIPELINES-05-TC13 2024/04/29 07:31:28 output: Now using project "releasetest-jp4sm" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:31:28 output: triggertemplate.triggers.tekton.dev/pipeline-template-git-pr created 2024/04/29 07:31:28 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] 2024/04/29 07:31:28 Verify SA "pipeline" is created in namespace "releasetest-jp4sm"  * Verify ServiceAccount "pipeline" exist ...[PASS] 2024/04/29 07:31:28 output: secret/github-secret created 2024/04/29 07:31:29 output:  * Create & Link secret "github-secret" to service account "pipeline" ...[PASS] 2024/04/29 07:31:29 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:False Severity: LastTransitionTime:{Inner:2024-04-29 07:31:28 +0000 UTC} Reason:MinimumReplicasUnavailable Message:Deployment does not have minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:31:28 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:31:28 +0000 UTC} Reason:ReplicaSetUpdated Message:ReplicaSet "el-listener-clustertriggerbinding-github-pr-575c7b9d46" is progressing.} {Type:Ready Status:False Severity: LastTransitionTime:{Inner:2024-04-29 07:31:28 +0000 UTC} Reason: Message:Condition Available has status: False with message: Deployment does not have minimum availability.} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:31:28 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc0004d6990 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-clustertriggerbinding-github-pr}} 2024/04/29 07:31:34 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:31:30 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:31:30 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:31:30 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-listener-clustertriggerbinding-github-pr-575c7b9d46" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:31:30 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:31:30 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000ce0e40 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-clustertriggerbinding-github-pr}} 2024/04/29 07:31:34 sinkpod name: el-listener-clustertriggerbinding-github-pr-575c7b9d46-wmzqg 2024/04/29 07:31:34 Route url: 'http://el-listener-clustertriggerbinding-github-pr-releasetest-jp4sm.apps.ci-op-bfkt0dtt-c64b7.cspilp.interop.ccitredhat.com'  * Expose Event listener "listener-clustertriggerbinding-github-pr" ...[PASS] 2024/04/29 07:31:39 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] 2024/04/29 07:31:39 validating pipeline run for success state... 2024/04/29 07:31:44 pipelineRun: pipelinerun-git-pr-ctb is successful under namespace : releasetest-jp4sm  * Verify pipelinerun |S.NO|pipeline_run_name |status |check_label_propagation| |----|----------------------|----------|-----------------------| |1 |pipelinerun-git-pr-ctb|successful|no | ...[PASS] 2024/04/29 07:31:44 Deleted EventListener 2024/04/29 07:31:49 EventListener's Deployment was deleted 2024/04/29 07:31:49 EventListener's Service was deleted 2024/04/29 07:31:49 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2024/04/29 07:32:04 output: project.project.openshift.io "releasetest-jp4sm" deleted  ## Create TriggersCRD resource with CEL interceptors (overlays): PIPELINES-05-TC15 2024/04/29 07:32:05 output: Now using project "releasetest-njqtb" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:32:05 output: eventlistener.triggers.tekton.dev/listener-triggerref created 2024/04/29 07:32:05 output: trigger.triggers.tekton.dev/trigger created 2024/04/29 07:32:05 output: triggerbinding.triggers.tekton.dev/github-pr-binding created 2024/04/29 07:32:05 output: triggertemplate.triggers.tekton.dev/github-template created 2024/04/29 07:32:06 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] 2024/04/29 07:32:06 Verify SA "pipeline" is created in namespace "releasetest-njqtb"  * Verify ServiceAccount "pipeline" exist ...[PASS] 2024/04/29 07:32:06 output: secret/github-secret created 2024/04/29 07:32:06 output:  * Create & Link secret "github-secret" to service account "pipeline" ...[PASS] 2024/04/29 07:32:06 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:False Severity: LastTransitionTime:{Inner:2024-04-29 07:32:05 +0000 UTC} Reason:MinimumReplicasUnavailable Message:Deployment does not have minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:32:05 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:32:05 +0000 UTC} Reason:ReplicaSetUpdated Message:ReplicaSet "el-listener-triggerref-686df59c77" is progressing.} {Type:Ready Status:False Severity: LastTransitionTime:{Inner:2024-04-29 07: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:2024-04-29 07:32:05 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc00063c6f0 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-triggerref}} 2024/04/29 07:32:11 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:32:07 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:32:07 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:32:07 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-listener-triggerref-686df59c77" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:32:07 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:32:07 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc00063c840 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-triggerref}} 2024/04/29 07:32:11 sinkpod name: el-listener-triggerref-686df59c77-g6lr9 2024/04/29 07:32:11 Route url: 'http://el-listener-triggerref-releasetest-njqtb.apps.ci-op-bfkt0dtt-c64b7.cspilp.interop.ccitredhat.com'  * Expose Event listener "listener-triggerref" ...[PASS] 2024/04/29 07:32:16 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] 2024/04/29 07:32:17 validating pipeline run for success state... 2024/04/29 07:32:52 pipelineRun: parallel-pipelinerun is successful under namespace : releasetest-njqtb  * Verify pipelinerun |S.NO|pipeline_run_name |status |check_label_propagation| |----|--------------------|----------|-----------------------| |1 |parallel-pipelinerun|successful|no | ...[PASS] 2024/04/29 07:32:52 Deleted EventListener 2024/04/29 07:32:52 EventListener's Deployment was deleted 2024/04/29 07:32:52 EventListener's Service was deleted 2024/04/29 07:32:52 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2024/04/29 07:33:07 output: project.project.openshift.io "releasetest-njqtb" deleted  ## Create Eventlistener with github interceptor And verify Kuberenetes Events: PIPELINES-05-TC17 2024/04/29 07:33:07 output: Now using project "releasetest-flflc" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:33:07 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 2024/04/29 07:33:08 output: triggerbinding.triggers.tekton.dev/pipeline-binding created 2024/04/29 07:33:08 output: triggertemplate.triggers.tekton.dev/pipeline-template created 2024/04/29 07:33:08 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] 2024/04/29 07:33:08 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[] Annotations:map[]} AddressStatus:{Address: Addresses:[]} Configuration:{GeneratedResourceName:}} 2024/04/29 07:33:13 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:33:10 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:33:10 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:33:10 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-listener-embed-binding-858ff99957" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:33:10 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:33:10 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000c21f20 Addresses:[]} Configuration:{GeneratedResourceName:el-listener-embed-binding}} 2024/04/29 07:33:13 sinkpod name: el-listener-embed-binding-858ff99957-vws74 2024/04/29 07:33:13 Route url: 'http://el-listener-embed-binding-releasetest-flflc.apps.ci-op-bfkt0dtt-c64b7.cspilp.interop.ccitredhat.com'  * Expose Event listener "listener-embed-binding" ...[PASS] 2024/04/29 07:33: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]  * Verify kubernetes events for eventlistener ...[PASS] 2024/04/29 07:33:19 validating pipeline run for success state... 2024/04/29 07:33:29 pipelineRun: simple-pipeline-run is successful under namespace : releasetest-flflc  * Verify pipelinerun |S.NO|pipeline_run_name |status |check_label_propagation| |----|-------------------|----------|-----------------------| |1 |simple-pipeline-run|successful|no | ...[PASS] 2024/04/29 07:33:29 Deleted EventListener 2024/04/29 07:33:29 EventListener's Deployment was deleted 2024/04/29 07:33:29 EventListener's Service was deleted 2024/04/29 07:33:29 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2024/04/29 07:33:44 output: project.project.openshift.io "releasetest-flflc" deleted # Verify triggerbindings spec  ## Verify CEL marshaljson function Test: PIPELINES-10-TC01 2024/04/29 07:33:44 output: Now using project "releasetest-qf8c5" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:33:44 output: eventlistener.triggers.tekton.dev/cel-marshaljson created  * Create |S.NO|resource_dir | |----|------------------------------------------------------| |1 |testdata/triggers/triggerbindings/cel-marshalJson.yaml| ...[PASS] 2024/04/29 07:33:44 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[] Annotations:map[]} AddressStatus:{Address: Addresses:[]} Configuration:{GeneratedResourceName:}} 2024/04/29 07:33:49 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:33:47 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:33:47 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:33:47 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-cel-marshaljson-7d9b954f6d" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:33:47 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:33:47 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc0006319b0 Addresses:[]} Configuration:{GeneratedResourceName:el-cel-marshaljson}} 2024/04/29 07:33:49 sinkpod name: el-cel-marshaljson-7d9b954f6d-l7cql 2024/04/29 07:33:50 Route url: 'http://el-cel-marshaljson-releasetest-qf8c5.apps.ci-op-bfkt0dtt-c64b7.cspilp.interop.ccitredhat.com'  * Expose Event listener "cel-marshaljson" ...[PASS] 2024/04/29 07:33:55 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] 2024/04/29 07:33:55 Waiting for TaskRun cel-trig-marshaljson in namespace releasetest-qf8c5 to succeed  * Verify taskrun |S.NO|task_run_name |status | |----|--------------------|-------| |1 |cel-trig-marshaljson|Success| ...[PASS] 2024/04/29 07:34:00 Deleted EventListener 2024/04/29 07:34:00 EventListener's Deployment was deleted 2024/04/29 07:34:00 EventListener's Service was deleted 2024/04/29 07:34:00 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2024/04/29 07:34:15 output: project.project.openshift.io "releasetest-qf8c5" deleted  ## Verify event message body parsing with old annotation Test: PIPELINES-10-TC02 2024/04/29 07:34:16 output: Now using project "releasetest-grtnq" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:34:16 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] 2024/04/29 07:34:16 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[] Annotations:map[]} AddressStatus:{Address: Addresses:[]} Configuration:{GeneratedResourceName:}} 2024/04/29 07:34:21 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:34:19 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:34:19 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:34:19 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-parse-json-body-with-annotation-bc87dcbdc" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:34:19 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:34:19 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc0004d7a40 Addresses:[]} Configuration:{GeneratedResourceName:el-parse-json-body-with-annotation}} 2024/04/29 07:34:21 sinkpod name: el-parse-json-body-with-annotation-bc87dcbdc-djwlv 2024/04/29 07:34:21 Route url: 'http://el-parse-json-body-with-annotation-releasetest-grtnq.apps.ci-op-bfkt0dtt-c64b7.cspilp.interop.ccitredhat.com'  * Expose Event listener "parse-json-body-with-annotation" ...[PASS] 2024/04/29 07:34:26 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] 2024/04/29 07:34:26 Waiting for TaskRun trig-parse-json-body-with-annotation in namespace releasetest-grtnq to succeed  * Verify taskrun |S.NO|task_run_name |status | |----|------------------------------------|-------| |1 |trig-parse-json-body-with-annotation|Success| ...[PASS] 2024/04/29 07:34:37 Deleted EventListener 2024/04/29 07:34:42 EventListener's Deployment was deleted 2024/04/29 07:34:42 EventListener's Service was deleted 2024/04/29 07:34:42 EventListener's Route got deleted successfully...  * Cleanup Triggers ...[PASS] 2024/04/29 07:34:57 output: project.project.openshift.io "releasetest-grtnq" deleted # Verify triggers tutorial  ## Run pipelines tutorial using triggers: PIPELINES-06-TC02 2024/04/29 07:34:57 output: Now using project "releasetest-c5wr7" on server "https://api.ci-op-bfkt0dtt-c64b7.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] 2024/04/29 07:34:57 Verify SA "pipeline" is created in namespace "releasetest-c5wr7"  * Verify ServiceAccount "pipeline" exist ...[PASS] 2024/04/29 07:35:02 output: task.tekton.dev/apply-manifests created 2024/04/29 07:35:03 output: task.tekton.dev/update-deployment created 2024/04/29 07:35:03 output: persistentvolumeclaim/source-pvc created 2024/04/29 07:35:03 output: pipeline.tekton.dev/build-and-deploy created 2024/04/29 07:35:03 output: triggerbinding.triggers.tekton.dev/vote-app created 2024/04/29 07:35:04 output: triggertemplate.triggers.tekton.dev/vote-app created 2024/04/29 07:35:04 output: trigger.triggers.tekton.dev/vote-trigger created secret/github-secret created 2024/04/29 07:35:04 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] 2024/04/29 07:35:04 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[] Annotations:map[]} AddressStatus:{Address: Addresses:[]} Configuration:{GeneratedResourceName:}} 2024/04/29 07:35:09 EventListenerStatus: {Status:{ObservedGeneration:0 Conditions:[{Type:Available Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:35:06 +0000 UTC} Reason:MinimumReplicasAvailable Message:Deployment has minimum availability.} {Type:Deployment Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:35:06 +0000 UTC} Reason: Message:Deployment exists} {Type:Progressing Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:35:06 +0000 UTC} Reason:NewReplicaSetAvailable Message:ReplicaSet "el-vote-app-7fdb79df59" has successfully progressed.} {Type:Ready Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:35:06 +0000 UTC} Reason: Message:EventListener is ready} {Type:Service Status:True Severity: LastTransitionTime:{Inner:2024-04-29 07:35:06 +0000 UTC} Reason: Message:Service exists}] Annotations:map[]} AddressStatus:{Address:0xc000c48210 Addresses:[]} Configuration:{GeneratedResourceName:el-vote-app}} 2024/04/29 07:35:09 sinkpod name: el-vote-app-7fdb79df59-b2g4f 2024/04/29 07:35:10 Route url: 'http://el-vote-app-releasetest-c5wr7.apps.ci-op-bfkt0dtt-c64b7.cspilp.interop.ccitredhat.com'  * Expose Event listener "vote-app" ...[PASS] 2024/04/29 07:35:15 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] 2024/04/29 07:35:15 validating pipeline run for success state... 2024/04/29 07:37:15 pipelineRun: build-deploy-pipelines-vote-api-jx92t is successful under namespace : releasetest-c5wr7  * Verify the latest pipelinerun for "successful" state ...[PASS] 2024/04/29 07:37:15 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] 2024/04/29 07:37:15 validating pipeline run for success state... 2024/04/29 07:39:16 pipelineRun: build-deploy-pipelines-vote-ui-kfb95 is successful under namespace : releasetest-c5wr7  * Verify the latest pipelinerun for "successful" state ...[PASS] 2024/04/29 07:39:16 Route url: 'http://pipelines-vote-ui-releasetest-c5wr7.apps.ci-op-bfkt0dtt-c64b7.cspilp.interop.ccitredhat.com'  * Get route url of the route "pipelines-vote-ui" ...[PASS]  * Validate route url for pipelines tutorial ...[FAIL] 2024/04/29 07:39:21 Skipping deletion of the namespace 'releasetest-c5wr7' as the test got failed Failed Step: Validate route url for pipelines tutorial Specification: specs/triggers/tutorial.spec:71 Error Message: [assertion failed: Command: lynx http://pipelines-vote-ui-releasetest-c5wr7.apps.ci-op-bfkt0dtt-c64b7.cspilp.interop.ccitredhat.com --dump ExitCode: 1 Error: exit status 1 Stdout: 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: * The host doesn't exist. Make sure the hostname was typed correctly and that a route matching this hostname exists. * The host exists, but doesn't have a matching path. Check if the URL path was typed correctly and that the route was created using the desired path. * Route and path matches, but all pods are down. Make sure that the resources exposed by this route (pods, services, deployment configs, etc) have at least one pod running. Stderr: Failures: ExitCode was 1 expected 0 Expected no error] Stacktrace: /alabama/go/pkg/mod/github.com/getgauge-contrib/gauge-go@v0.4.0/testsuit/testing.go:46 github.com/openshift-pipelines/release-tests/pkg/cmd.testsuitAdaptor.Log(...) /tmp/release-tests/pkg/cmd/cmd.go:34 gotest.tools/v3/internal/assert.RunComparison({0x7f9744670fd8, 0x4fff5c0}, 0x374e608, 0xc000d26140, {0x0, 0x0, 0x0}) /alabama/go/pkg/mod/gotest.tools/v3@v3.5.1/internal/assert/result.go:60 +0x43f gotest.tools/v3/internal/assert.Eval({0x7f9744670fd8, 0x4fff5c0}, 0x4fff5c0?, {0x31847c0?, 0xc000d26140?}, {0x0, 0x0, 0x0}) /alabama/go/pkg/mod/gotest.tools/v3@v3.5.1/internal/assert/assert.go:56 +0x21c gotest.tools/v3/assert.Assert({0x39ce2d8, 0x4fff5c0}, {0x31847c0, 0xc000d26140}, {0x0, 0x0, 0x0}) /alabama/go/pkg/mod/gotest.tools/v3@v3.5.1/assert/assert.go:145 +0x9c gotest.tools/v3/icmd.(*Result).Assert(0xc000a2c6c0, {0x39ce2d8, 0x4fff5c0}, {0x0, 0x0, {0x0, 0x0}, {0x0, 0x0}, {0x0, ...}}) /alabama/go/pkg/mod/gotest.tools/v3@v3.5.1/icmd/command.go:62 +0x135 github.com/openshift-pipelines/release-tests/pkg/cmd.Assert({0x0, 0x0, {0x0, 0x0}, {0x0, 0x0}, {0x0, 0x0}}, {0xc0005e2810, 0x3, ...}) /tmp/release-tests/pkg/cmd/cmd.go:50 +0x105 github.com/openshift-pipelines/release-tests/pkg/cmd.MustSucceed(...) /tmp/release-tests/pkg/cmd/cmd.go:43 github.com/openshift-pipelines/release-tests/steps/utility.glob..func4() /tmp/release-tests/steps/utility/utility.go:47 +0x11a reflect.Value.call({0x30131e0?, 0x374e1a8?, 0x7f974476a508?}, {0x35f7eb8, 0x4}, {0x4fff5c0, 0x0, 0x0?}) /usr/lib/golang/src/reflect/value.go:596 +0xce7 reflect.Value.Call({0x30131e0?, 0x374e1a8?, 0x5d?}, {0x4fff5c0?, 0xc0005dfc30?, 0x17456ab?}) /usr/lib/golang/src/reflect/value.go:380 +0xb9 github.com/getgauge-contrib/gauge-go/testsuit.executeFunc({0x30131e0?, 0x374e1a8?, 0x64?}, {0x0, 0x0, 0xc00078e220?}) /alabama/go/pkg/mod/github.com/getgauge-contrib/gauge-go@v0.4.0/testsuit/funcExecutor.go:47 +0x238 github.com/getgauge-contrib/gauge-go/testsuit.(*Step).Execute(0xc00048fc80?, {0x0?, 0x29?, 0x5f?}) /alabama/go/pkg/mod/github.com/getgauge-contrib/gauge-go@v0.4.0/testsuit/step.go:17 +0x8b github.com/getgauge-contrib/gauge-go/messageprocessors.(*ExecuteStepProcessor).Process(0x323de80?, 0xc000b5e4b0, 0xc000000007?) /alabama/go/pkg/mod/github.com/getgauge-contrib/gauge-go@v0.4.0/messageprocessors/ExecuteStepProcessor.go:20 +0xa6 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 +0x21f command-line-arguments.init.0() /tmp/gauge_temp1714375371632239213/gauge_test.go:32 +0xf  Successfully generated xml-report to => /logs/artifacts/xml-report/2024-04-29 07.39.21 Transformed SuiteResult to report structure Successfully generated html-report to => /logs/artifacts/html-report/2024-04-29_07.39.21/index.html Done generating HTML report using theme from /tmp/plugins/html-report/4.3.1/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 986.171s Runner with PID:27608 has exited Specifications: 4 executed 3 passed 1 failed 0 skipped Scenarios: 10 executed 9 passed 1 failed 0 skipped Total time taken: 16m26.08s 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: 38567 Successfully made the connection with plugin with port: 38567 Starting Xml Report plugin Attempting to connect to grpc server at port: 37295 Successfully made the connection with plugin with port: 37295 Initialising suite data store. # Verify openshift pipelines monitoring  ## Openshift pipelines metrics acceptance tests: PIPELINES-01-TC01 2024/04/29 07:39:26 output: Now using project "releasetest-7m8sq" on server "https://api.ci-op-bfkt0dtt-c64b7.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 2024/04/29 07:39:26 Waiting for operator to be up and running.... 2024/04/29 07:39:26 Operator is up  * Validate Operator should be installed ...[PASS] 2024/04/29 07:39:26 Target Job: [node-exporter] ready/up status, Actual: [1], Expected: [1] 2024/04/29 07:39:26 Target Job: [kube-state-metrics] ready/up status, Actual: [1], Expected: [1] 2024/04/29 07:39:27 Target Job: [prometheus-k8s] ready/up status, Actual: [1], Expected: [1] 2024/04/29 07:39:27 Target Job: [prometheus-operator] ready/up status, Actual: [1], Expected: [1] 2024/04/29 07:39:27 Target Job: [alertmanager-main] ready/up status, Actual: [1], Expected: [1] 2024/04/29 07:39:27 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] 2024/04/29 07:39:34 output: project.project.openshift.io "releasetest-7m8sq" deleted Transformed SuiteResult to report structure Successfully generated html-report to => /logs/artifacts/html-report/2024-04-29_07.39.34/index.html Done generating HTML report using theme from /tmp/plugins/html-report/4.3.1/themes/default Successfully generated xml-report to => /logs/artifacts/xml-report/2024-04-29 07.39.34 Sending kill message to Html Report plugin. Sending kill message to Xml Report plugin. Sending kill message to runner. ok command-line-arguments 8.725s Runner with PID:29993 has exited Specifications: 1 executed 1 passed 0 failed 0 skipped Scenarios: 1 executed 1 passed 0 failed 0 skipped Total time taken: 8.659s Updates are available. Run `gauge update -c` for more info. gauge run specs/operator/addon.spec specs/operator/auto-prune.spec log-level : [debug] parallel : [true] 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. 2 specifications parsing completed. Applying tags filter: sanity & !tls The following specifications satisfy filter criteria: specs/operator/addon.spec 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: 42421 Successfully made the connection with plugin with port: 42421 Starting Xml Report plugin Attempting to connect to grpc server at port: 43139 Successfully made the connection with plugin with port: 43139 Executing in 2 parallel streams. Starting go runner Established connection to runner. Initialising suite data store. Initialising suite data store. [runner: 1] # Verify Addon E2E spec [runner: 2] # Verify auto-prune E2E [runner: 1] ## Disable/Enable community clustertasks: PIPELINES-15-TC01 2024/04/29 07:39:44 output: Now using project "releasetest-w84vr" on server "https://api.ci-op-bfkt0dtt-c64b7.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 [runner: 1] * Validate Operator should be installed 2024/04/29 07:39:44 output: Now using project "releasetest-8kl5f" on server "https://api.ci-op-bfkt0dtt-c64b7.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 2024/04/29 07:39:45 Annotating the namespaces with 'operator.tekton.dev/prune.skip=true' so that the pipelineruns should not get deleted 2024/04/29 07:39:45 Waiting for operator to be up and running.... 2024/04/29 07:39:45 Operator is up [runner: 1] * Update addon config with clusterTasks as "true" communityClustertasks as "true" and pipelineTemplates as "true" and expect message "" 2024/04/29 07:39:45 output: namespace/openshift annotated 2024/04/29 07:39:45 output: tektonconfig.operator.tekton.dev/config patched [runner: 1] * "community" clustertasks are "present" 2024/04/29 07:39:45 Checking if clustertasks jib-maven,helm-upgrade-from-source,helm-upgrade-from-repo,trigger-jenkins-job,git-cli,pull-request,kubeconfig-creator,argocd-task-sync-and-wait is/are present 2024/04/29 07:39:45 output: namespace/releasetest-8kl5f annotated 2024/04/29 07:39:45 output: namespace/releasetest-c5wr7 annotated 2024/04/29 07:39:45 output: namespace/releasetest-w84vr annotated [runner: 2] ## Verify auto prune for taskrun: PIPELINES-12-TC01 2024/04/29 07:39:46 output: Now using project "releasetest-vt6qf" on server "https://api.ci-op-bfkt0dtt-c64b7.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 [runner: 2] * Validate Operator should be installed 2024/04/29 07:39:46 Waiting for operator to be up and running.... 2024/04/29 07:39:46 Waiting for config cr InstalledStatus Actual: [False] Expected: [True] 2024/04/29 07:39:50 Verifying if the clustertask jib-maven is present 2024/04/29 07:39:50 Clustertask jib-maven is present 2024/04/29 07:39:51 Operator is up [runner: 2] * Verify ServiceAccount "pipeline" exist 2024/04/29 07:39:51 Verify SA "pipeline" is created in namespace "releasetest-vt6qf" [runner: 2] * Remove auto pruner configuration from config CR 2024/04/29 07:39:51 Removing pruner configuration from config CR [runner: 2] * 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 | 2024/04/29 07:39:52 output: task.tekton.dev/echo-task-pipeline created pipeline.tekton.dev/echo-pipeline created 2024/04/29 07:39:52 output: pipelinerun.tekton.dev/echo-pipeline-run-7dzfn created pipelinerun.tekton.dev/echo-pipeline-run-mf9xs created pipelinerun.tekton.dev/echo-pipeline-run-mdp4r created pipelinerun.tekton.dev/echo-pipeline-run-lqtwx created pipelinerun.tekton.dev/echo-pipeline-run-pn2mf created 2024/04/29 07:39:53 output: task.tekton.dev/echo-task created 2024/04/29 07:39:53 output: taskrun.tekton.dev/echo-task-run-4ft4r created taskrun.tekton.dev/echo-task-run-ns4rn created taskrun.tekton.dev/echo-task-run-66m6k created taskrun.tekton.dev/echo-task-run-9jfjx created taskrun.tekton.dev/echo-task-run-4t7wb created [runner: 2] * Update pruner config "with" keep "2" schedule "*/1 * * * *" resources "taskrun" and "without" keep-since "" 2024/04/29 07:39:53 output: tektonconfig.operator.tekton.dev/config patched [runner: 2] * Assert if cronjob with prefix "tekton-resource-pruner" is "present" in target namespace 2024/04/29 07:39:53 Verifying if the cronjob tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:39:55 Verifying if the clustertask helm-upgrade-from-source is present 2024/04/29 07:39:55 Clustertask helm-upgrade-from-source is present 2024/04/29 07:39:58 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:39:58 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines [runner: 2] * "2" taskrun(s) should be present within "120" seconds 2024/04/29 07:39:58 Verifying if 2 number of taskruns are present 2024/04/29 07:40:00 Verifying if the clustertask helm-upgrade-from-repo is present 2024/04/29 07:40:00 Clustertask helm-upgrade-from-repo is present 2024/04/29 07:40:05 Verifying if the clustertask trigger-jenkins-job is present 2024/04/29 07:40:05 Clustertask trigger-jenkins-job is present [runner: 2] * "5" pipelinerun(s) should be present within "120" seconds 2024/04/29 07:40:08 Verifying if 5 number of pipelinerun are present 2024/04/29 07:40:10 Verifying if the clustertask git-cli is present 2024/04/29 07:40:10 Clustertask git-cli is present [runner: 2] * Remove auto pruner configuration from config CR 2024/04/29 07:40:13 Removing pruner configuration from config CR [runner: 2] * Assert if cronjob with prefix "tekton-resource-pruner" is "not present" in target namespace 2024/04/29 07:40:14 Verifying if the cronjob tekton-resource-pruner is not present in namespace openshift-pipelines 2024/04/29 07:40:15 Verifying if the clustertask pull-request is present 2024/04/29 07:40:15 Clustertask pull-request is present 2024/04/29 07:40:19 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:40:19 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:40:20 Verifying if the clustertask kubeconfig-creator is present 2024/04/29 07:40:20 Clustertask kubeconfig-creator is present 2024/04/29 07:40:25 Verifying if the clustertask argocd-task-sync-and-wait is present 2024/04/29 07:40:25 Clustertask argocd-task-sync-and-wait is present [runner: 1] * "tkn,openshift-client" clustertasks are "present" 2024/04/29 07:40:25 Checking if clustertasks tkn,openshift-client is/are present 2024/04/29 07:40:30 Verifying if the clustertask tkn is present 2024/04/29 07:40:30 Clustertask tkn is present 2024/04/29 07:40:34 output: project.project.openshift.io "releasetest-vt6qf" deleted [runner: 2] ## Verify auto prune with keep-since: PIPELINES-12-TC04 2024/04/29 07:40:34 output: Now using project "releasetest-8pwd8" on server "https://api.ci-op-bfkt0dtt-c64b7.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 [runner: 2] * Validate Operator should be installed [runner: 2] * Verify ServiceAccount "pipeline" exist 2024/04/29 07:40:34 Verify SA "pipeline" is created in namespace "releasetest-8pwd8" 2024/04/29 07:40:35 Verifying if the clustertask openshift-client is present 2024/04/29 07:40:35 Clustertask openshift-client is present [runner: 1] * Update addon config with clusterTasks as "true" communityClustertasks as "false" and pipelineTemplates as "true" and expect message "" 2024/04/29 07:40:35 output: tektonconfig.operator.tekton.dev/config patched [runner: 1] * "community" clustertasks are "not present" 2024/04/29 07:40:35 Checking if clustertasks jib-maven,helm-upgrade-from-source,helm-upgrade-from-repo,trigger-jenkins-job,git-cli,pull-request,kubeconfig-creator,argocd-task-sync-and-wait is/are not present [runner: 2] * Remove auto pruner configuration from config CR 2024/04/29 07:40:39 Removing pruner configuration from config CR [runner: 2] * 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 | 2024/04/29 07:40:39 output: task.tekton.dev/echo-task-pipeline created pipeline.tekton.dev/echo-pipeline created 2024/04/29 07:40:39 output: pipelinerun.tekton.dev/echo-pipeline-run-pnbsc created pipelinerun.tekton.dev/echo-pipeline-run-mffbp created pipelinerun.tekton.dev/echo-pipeline-run-lmkdd created pipelinerun.tekton.dev/echo-pipeline-run-lxv44 created pipelinerun.tekton.dev/echo-pipeline-run-lqgmq created 2024/04/29 07:40:40 output: task.tekton.dev/echo-task created 2024/04/29 07:40:40 output: taskrun.tekton.dev/echo-task-run-rbbm7 created taskrun.tekton.dev/echo-task-run-jcwfj created taskrun.tekton.dev/echo-task-run-7dnft created taskrun.tekton.dev/echo-task-run-snvfs created taskrun.tekton.dev/echo-task-run-fxmbf created [runner: 2] * Sleep for "120" seconds 2024/04/29 07:40:40 Sleeping for 120 seconds 2024/04/29 07:40:40 Verifying if the clustertask jib-maven is not present 2024/04/29 07:40:40 Clustertask jib-maven is not present 2024/04/29 07:40:45 Verifying if the clustertask helm-upgrade-from-source is not present 2024/04/29 07:40:45 Clustertask helm-upgrade-from-source is not present 2024/04/29 07:40:50 Verifying if the clustertask helm-upgrade-from-repo is not present 2024/04/29 07:40:50 Clustertask helm-upgrade-from-repo is not present 2024/04/29 07:40:55 Verifying if the clustertask trigger-jenkins-job is not present 2024/04/29 07:40:55 Clustertask trigger-jenkins-job is not present 2024/04/29 07:41:00 Verifying if the clustertask git-cli is not present 2024/04/29 07:41:00 Clustertask git-cli is not present 2024/04/29 07:41:05 Verifying if the clustertask pull-request is not present 2024/04/29 07:41:05 Clustertask pull-request is not present 2024/04/29 07:41:10 Verifying if the clustertask kubeconfig-creator is not present 2024/04/29 07:41:11 Clustertask kubeconfig-creator is not present 2024/04/29 07:41:16 Verifying if the clustertask argocd-task-sync-and-wait is not present 2024/04/29 07:41:16 Clustertask argocd-task-sync-and-wait is not present [runner: 1] * "tkn,openshift-client" clustertasks are "present" 2024/04/29 07:41:16 Checking if clustertasks tkn,openshift-client is/are present 2024/04/29 07:41:21 Verifying if the clustertask tkn is present 2024/04/29 07:41:21 Clustertask tkn is present 2024/04/29 07:41:26 Verifying if the clustertask openshift-client is present 2024/04/29 07:41:26 Clustertask openshift-client is present [runner: 1] * Update addon config with clusterTasks as "true" communityClustertasks as "true" and pipelineTemplates as "true" and expect message "" 2024/04/29 07:41:26 output: tektonconfig.operator.tekton.dev/config patched [runner: 1] * "community" clustertasks are "present" 2024/04/29 07:41:26 Checking if clustertasks jib-maven,helm-upgrade-from-source,helm-upgrade-from-repo,trigger-jenkins-job,git-cli,pull-request,kubeconfig-creator,argocd-task-sync-and-wait is/are present 2024/04/29 07:41:31 Verifying if the clustertask jib-maven is present 2024/04/29 07:41:31 Clustertask jib-maven is present 2024/04/29 07:41:36 Verifying if the clustertask helm-upgrade-from-source is present 2024/04/29 07:41:36 Clustertask helm-upgrade-from-source is present 2024/04/29 07:41:41 Verifying if the clustertask helm-upgrade-from-repo is present 2024/04/29 07:41:41 Clustertask helm-upgrade-from-repo is present 2024/04/29 07:41:46 Verifying if the clustertask trigger-jenkins-job is present 2024/04/29 07:41:46 Clustertask trigger-jenkins-job is present 2024/04/29 07:41:51 Verifying if the clustertask git-cli is present 2024/04/29 07:41:51 Clustertask git-cli is present 2024/04/29 07:41:56 Verifying if the clustertask pull-request is present 2024/04/29 07:41:56 Clustertask pull-request is present 2024/04/29 07:42:01 Verifying if the clustertask kubeconfig-creator is present 2024/04/29 07:42:01 Clustertask kubeconfig-creator is present 2024/04/29 07:42:06 Verifying if the clustertask argocd-task-sync-and-wait is present 2024/04/29 07:42:06 Clustertask argocd-task-sync-and-wait is present [runner: 1] * "tkn,openshift-client" clustertasks are "present" 2024/04/29 07:42:06 Checking if clustertasks tkn,openshift-client is/are present 2024/04/29 07:42:11 Verifying if the clustertask tkn is present 2024/04/29 07:42:11 Clustertask tkn is present 2024/04/29 07:42:16 Verifying if the clustertask openshift-client is present 2024/04/29 07:42:16 Clustertask openshift-client is present 2024/04/29 07:42:23 output: project.project.openshift.io "releasetest-w84vr" deleted [runner: 1] ## Disable/Enable clustertasks: PIPELINES-15-TC02 2024/04/29 07:42:24 output: Now using project "releasetest-fpcc5" on server "https://api.ci-op-bfkt0dtt-c64b7.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 [runner: 1] * Validate Operator should be installed [runner: 1] * Update addon config with clusterTasks as "true" communityClustertasks as "true" and pipelineTemplates as "true" and expect message "" 2024/04/29 07:42:24 output: tektonconfig.operator.tekton.dev/config patched (no change) [runner: 1] * "community" clustertasks are "present" 2024/04/29 07:42:24 Checking if clustertasks jib-maven,helm-upgrade-from-source,helm-upgrade-from-repo,trigger-jenkins-job,git-cli,pull-request,kubeconfig-creator,argocd-task-sync-and-wait is/are present 2024/04/29 07:42:29 Verifying if the clustertask jib-maven is present 2024/04/29 07:42:29 Clustertask jib-maven is present 2024/04/29 07:42:34 Verifying if the clustertask helm-upgrade-from-source is present 2024/04/29 07:42:34 Clustertask helm-upgrade-from-source is present 2024/04/29 07:42:39 Verifying if the clustertask helm-upgrade-from-repo is present 2024/04/29 07:42:39 Clustertask helm-upgrade-from-repo is present [runner: 2] * Create |S.NO|resource_dir | |----|----------------------------------------------------| |1 |testdata/pruner/pipeline/pipelinerun-for-pruner.yaml| |2 |testdata/pruner/task/taskrun-for-pruner.yaml | 2024/04/29 07:42:40 output: pipelinerun.tekton.dev/echo-pipeline-run-mn7lc created pipelinerun.tekton.dev/echo-pipeline-run-wlx8m created pipelinerun.tekton.dev/echo-pipeline-run-jq47x created pipelinerun.tekton.dev/echo-pipeline-run-xpw4r created pipelinerun.tekton.dev/echo-pipeline-run-kwcnx created 2024/04/29 07:42:40 output: taskrun.tekton.dev/echo-task-run-nnmzg created taskrun.tekton.dev/echo-task-run-mzf2b created taskrun.tekton.dev/echo-task-run-wcm5m created taskrun.tekton.dev/echo-task-run-cm92s created taskrun.tekton.dev/echo-task-run-dtqxr created [runner: 2] * Update pruner config "without" keep "" schedule "*/1 * * * *" resources "pipelinerun,taskrun" and "with" keep-since "2" 2024/04/29 07:42:40 output: tektonconfig.operator.tekton.dev/config patched [runner: 2] * Assert if cronjob with prefix "tekton-resource-pruner" is "present" in target namespace 2024/04/29 07:42:40 Verifying if the cronjob tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:42:44 Verifying if the clustertask trigger-jenkins-job is present 2024/04/29 07:42:44 Clustertask trigger-jenkins-job is present 2024/04/29 07:42:45 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:42:45 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines [runner: 2] * "5" pipelinerun(s) should be present within "120" seconds 2024/04/29 07:42:45 Verifying if 5 number of pipelinerun are present 2024/04/29 07:42:49 Verifying if the clustertask git-cli is present 2024/04/29 07:42:49 Clustertask git-cli is present 2024/04/29 07:42:54 Verifying if the clustertask pull-request is present 2024/04/29 07:42:54 Clustertask pull-request is present 2024/04/29 07:42:59 Verifying if the clustertask kubeconfig-creator is present 2024/04/29 07:42:59 Clustertask kubeconfig-creator is present 2024/04/29 07:43:04 Verifying if the clustertask argocd-task-sync-and-wait is present 2024/04/29 07:43:04 Clustertask argocd-task-sync-and-wait is present [runner: 1] * "tkn,openshift-client" clustertasks are "present" 2024/04/29 07:43:04 Checking if clustertasks tkn,openshift-client is/are present [runner: 2] * "10" taskrun(s) should be present within "120" seconds 2024/04/29 07:43:05 Verifying if 10 number of taskruns are present 2024/04/29 07:43:09 Verifying if the clustertask tkn is present 2024/04/29 07:43:09 Clustertask tkn is present [runner: 2] * Remove auto pruner configuration from config CR 2024/04/29 07:43:11 Removing pruner configuration from config CR [runner: 2] * Assert if cronjob with prefix "tekton-resource-pruner" is "not present" in target namespace 2024/04/29 07:43:11 Verifying if the cronjob tekton-resource-pruner is not present in namespace openshift-pipelines 2024/04/29 07:43:14 Verifying if the clustertask openshift-client is present 2024/04/29 07:43:14 Clustertask openshift-client is present [runner: 1] * Assert pipelines are "present" in "openshift" namespace 2024/04/29 07:43:16 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:43:16 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:43:19 Verifying that 27 pipelines are present in namespace openshift 2024/04/29 07:43:19 Pipelines are present in namespace openshift [runner: 1] * Update addon config with clusterTasks as "false" communityClustertasks as "false" and pipelineTemplates as "false" and expect message "" 2024/04/29 07:43:19 output: tektonconfig.operator.tekton.dev/config patched [runner: 1] * "community" clustertasks are "not present" 2024/04/29 07:43:19 Checking if clustertasks jib-maven,helm-upgrade-from-source,helm-upgrade-from-repo,trigger-jenkins-job,git-cli,pull-request,kubeconfig-creator,argocd-task-sync-and-wait is/are not present 2024/04/29 07:43:24 Verifying if the clustertask jib-maven is not present 2024/04/29 07:43:24 Clustertask jib-maven is not present 2024/04/29 07:43:29 Verifying if the clustertask helm-upgrade-from-source is not present 2024/04/29 07:43:30 Clustertask helm-upgrade-from-source is not present 2024/04/29 07:43:31 output: project.project.openshift.io "releasetest-8pwd8" deleted [runner: 2] ## Verify auto prune add resources taskrun and pipelinerun per namespace with annotation: PIPELINES-12-TC07 2024/04/29 07:43:31 output: Now using project "releasetest-475bv" on server "https://api.ci-op-bfkt0dtt-c64b7.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 [runner: 2] * Validate Operator should be installed [runner: 2] * Verify ServiceAccount "pipeline" exist 2024/04/29 07:43:31 Verify SA "pipeline" is created in namespace "releasetest-475bv" 2024/04/29 07:43:35 Verifying if the clustertask helm-upgrade-from-repo is not present 2024/04/29 07:43:35 Clustertask helm-upgrade-from-repo is not present [runner: 2] * Remove auto pruner configuration from config CR 2024/04/29 07:43:36 Removing pruner configuration from config CR [runner: 2] * 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 | 2024/04/29 07:43:36 output: task.tekton.dev/echo-task-pipeline created pipeline.tekton.dev/echo-pipeline created 2024/04/29 07:43:37 output: pipelinerun.tekton.dev/echo-pipeline-run-nhtjx created pipelinerun.tekton.dev/echo-pipeline-run-rssnx created pipelinerun.tekton.dev/echo-pipeline-run-728h9 created pipelinerun.tekton.dev/echo-pipeline-run-sjvqw created pipelinerun.tekton.dev/echo-pipeline-run-5nn6n created 2024/04/29 07:43:37 output: task.tekton.dev/echo-task created 2024/04/29 07:43:37 output: taskrun.tekton.dev/echo-task-run-n529p created taskrun.tekton.dev/echo-task-run-z8w57 created taskrun.tekton.dev/echo-task-run-dwdxc created taskrun.tekton.dev/echo-task-run-zc6j9 created taskrun.tekton.dev/echo-task-run-9q6v6 created [runner: 2] * Annotate namespace with "operator.tekton.dev/prune.resources=pipelinerun,taskrun" 2024/04/29 07:43:37 Annotating namespace releasetest-475bv with operator.tekton.dev/prune.resources=pipelinerun,taskrun 2024/04/29 07:43:37 output: namespace/releasetest-475bv annotated [runner: 2] * Update pruner config "with" keep "2" schedule "*/1 * * * *" resources "taskrun" and "without" keep-since "" 2024/04/29 07:43:38 output: tektonconfig.operator.tekton.dev/config patched [runner: 2] * Assert if cronjob with prefix "tekton-resource-pruner" is "present" in target namespace 2024/04/29 07:43:38 Verifying if the cronjob tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:43:40 Verifying if the clustertask trigger-jenkins-job is not present 2024/04/29 07:43:40 Clustertask trigger-jenkins-job is not present 2024/04/29 07:43:43 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:43:43 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines [runner: 2] * "2" pipelinerun(s) should be present within "120" seconds 2024/04/29 07:43:43 Verifying if 2 number of pipelinerun are present 2024/04/29 07:43:45 Verifying if the clustertask git-cli is not present 2024/04/29 07:43:45 Clustertask git-cli is not present 2024/04/29 07:43:50 Verifying if the clustertask pull-request is not present 2024/04/29 07:43:50 Clustertask pull-request is not present 2024/04/29 07:43:55 Verifying if the clustertask kubeconfig-creator is not present 2024/04/29 07:43:55 Clustertask kubeconfig-creator is not present 2024/04/29 07:44:00 Verifying if the clustertask argocd-task-sync-and-wait is not present 2024/04/29 07:44:00 Clustertask argocd-task-sync-and-wait is not present [runner: 1] * "tkn,openshift-client" clustertasks are "not present" 2024/04/29 07:44:00 Checking if clustertasks tkn,openshift-client is/are not present [runner: 2] * "2" taskrun(s) should be present within "120" seconds 2024/04/29 07:44:03 Verifying if 2 number of taskruns are present 2024/04/29 07:44:05 Verifying if the clustertask tkn is not present 2024/04/29 07:44:05 Clustertask tkn is not present [runner: 2] * Remove annotation "operator.tekton.dev/prune.resources" from namespace 2024/04/29 07:44:08 Removing annotation releasetest-475bv from namespace operator.tekton.dev/prune.resources 2024/04/29 07:44:08 output: namespace/releasetest-475bv annotated [runner: 2] * Create |S.NO|resource_dir | |----|----------------------------------------------------| |1 |testdata/pruner/pipeline/pipelinerun-for-pruner.yaml| |2 |testdata/pruner/task/taskrun-for-pruner.yaml | 2024/04/29 07:44:08 output: pipelinerun.tekton.dev/echo-pipeline-run-666f5 created pipelinerun.tekton.dev/echo-pipeline-run-g9bcb created pipelinerun.tekton.dev/echo-pipeline-run-9fxsg created pipelinerun.tekton.dev/echo-pipeline-run-t98nb created pipelinerun.tekton.dev/echo-pipeline-run-tqzn5 created 2024/04/29 07:44:08 output: taskrun.tekton.dev/echo-task-run-w7tbf created taskrun.tekton.dev/echo-task-run-b8pld created taskrun.tekton.dev/echo-task-run-qsqhd created taskrun.tekton.dev/echo-task-run-76lml created taskrun.tekton.dev/echo-task-run-khx8g created [runner: 2] * "7" pipelinerun(s) should be present within "120" seconds 2024/04/29 07:44:08 Verifying if 7 number of pipelinerun are present 2024/04/29 07:44:10 Verifying if the clustertask openshift-client is not present 2024/04/29 07:44:10 Clustertask openshift-client is not present [runner: 1] * Assert pipelines are "not present" in "openshift" namespace [runner: 2] * "2" taskrun(s) should be present within "120" seconds 2024/04/29 07:44:13 Verifying if 2 number of taskruns are present 2024/04/29 07:44:15 Verifying if 0 pipelines are not present in namespace openshift 2024/04/29 07:44:15 Pipelines are present in namespace openshift [runner: 1] * Update addon config with clusterTasks as "true" communityClustertasks as "true" and pipelineTemplates as "true" and expect message "" 2024/04/29 07:44:15 output: tektonconfig.operator.tekton.dev/config patched [runner: 1] * "community" clustertasks are "present" 2024/04/29 07:44:15 Checking if clustertasks jib-maven,helm-upgrade-from-source,helm-upgrade-from-repo,trigger-jenkins-job,git-cli,pull-request,kubeconfig-creator,argocd-task-sync-and-wait is/are present 2024/04/29 07:44:20 Verifying if the clustertask jib-maven is present 2024/04/29 07:44:20 Clustertask jib-maven is present 2024/04/29 07:44:25 Verifying if the clustertask helm-upgrade-from-source is present 2024/04/29 07:44:25 Clustertask helm-upgrade-from-source is present 2024/04/29 07:44:30 Verifying if the clustertask helm-upgrade-from-repo is present 2024/04/29 07:44:30 Clustertask helm-upgrade-from-repo is present 2024/04/29 07:44:35 Verifying if the clustertask trigger-jenkins-job is present 2024/04/29 07:44:35 Clustertask trigger-jenkins-job is present 2024/04/29 07:44:40 Verifying if the clustertask git-cli is present 2024/04/29 07:44:40 Clustertask git-cli is present 2024/04/29 07:44:45 Verifying if the clustertask pull-request is present 2024/04/29 07:44:45 Clustertask pull-request is present 2024/04/29 07:44:50 Verifying if the clustertask kubeconfig-creator is present 2024/04/29 07:44:50 Clustertask kubeconfig-creator is present 2024/04/29 07:44:55 Verifying if the clustertask argocd-task-sync-and-wait is present 2024/04/29 07:44:55 Clustertask argocd-task-sync-and-wait is present [runner: 1] * "tkn,openshift-client" clustertasks are "present" 2024/04/29 07:44:55 Checking if clustertasks tkn,openshift-client is/are present 2024/04/29 07:45:00 Verifying if the clustertask tkn is present 2024/04/29 07:45:00 Clustertask tkn is present [runner: 2] * Remove auto pruner configuration from config CR 2024/04/29 07:45:03 Removing pruner configuration from config CR [runner: 2] * Assert if cronjob with prefix "tekton-resource-pruner" is "not present" in target namespace 2024/04/29 07:45:04 Verifying if the cronjob tekton-resource-pruner is not present in namespace openshift-pipelines 2024/04/29 07:45:05 Verifying if the clustertask openshift-client is present 2024/04/29 07:45:05 Clustertask openshift-client is present [runner: 1] * Assert pipelines are "present" in "openshift" namespace 2024/04/29 07:45:09 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:45:09 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:45:10 Verifying that 27 pipelines are present in namespace openshift 2024/04/29 07:45:10 Pipelines are present in namespace openshift 2024/04/29 07:45:17 output: project.project.openshift.io "releasetest-fpcc5" deleted [runner: 1] ## Disable/Enable pipeline templates: PIPELINES-15-TC03 2024/04/29 07:45:17 output: Now using project "releasetest-d84vj" on server "https://api.ci-op-bfkt0dtt-c64b7.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 [runner: 1] * Validate Operator should be installed [runner: 1] * Update addon config with clusterTasks as "true" communityClustertasks as "true" and pipelineTemplates as "true" and expect message "" 2024/04/29 07:45:18 output: tektonconfig.operator.tekton.dev/config patched (no change) [runner: 1] * Assert pipelines are "present" in "openshift" namespace 2024/04/29 07:45:23 Verifying that 27 pipelines are present in namespace openshift 2024/04/29 07:45:23 Pipelines are present in namespace openshift [runner: 1] * Update addon config with clusterTasks as "true" communityClustertasks as "true" and pipelineTemplates as "false" and expect message "" 2024/04/29 07:45:23 output: tektonconfig.operator.tekton.dev/config patched [runner: 1] * Assert pipelines are "not present" in "openshift" namespace 2024/04/29 07:45:24 output: project.project.openshift.io "releasetest-475bv" deleted [runner: 2] ## Verify auto prune cronjob contains single container: PIPELINES-12-TC14 2024/04/29 07:45:24 output: Now using project "releasetest-xz654" on server "https://api.ci-op-bfkt0dtt-c64b7.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 [runner: 2] * Validate Operator should be installed [runner: 2] * Update pruner config "with" keep "2" schedule "20 * * * *" resources "taskrun" and "without" keep-since "" 2024/04/29 07:45:24 output: tektonconfig.operator.tekton.dev/config patched [runner: 2] * Create project "test-project-1" 2024/04/29 07:45:24 Check if project test-project-1 already exists 2024/04/29 07:45:24 Creating project test-project-1 2024/04/29 07:45:25 output: Now using project "test-project-1" on server "https://api.ci-op-bfkt0dtt-c64b7.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 [runner: 2] * Create project "test-project-2" 2024/04/29 07:45:25 Check if project test-project-2 already exists 2024/04/29 07:45:25 Creating project test-project-2 2024/04/29 07:45:25 output: Now using project "test-project-2" on server "https://api.ci-op-bfkt0dtt-c64b7.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 [runner: 2] * Sleep for "10" seconds 2024/04/29 07:45:25 Sleeping for 10 seconds 2024/04/29 07:45:28 Verifying if 0 pipelines are not present in namespace openshift 2024/04/29 07:45:28 Pipelines are present in namespace openshift [runner: 1] * Update addon config with clusterTasks as "true" communityClustertasks as "true" and pipelineTemplates as "true" and expect message "" 2024/04/29 07:45:28 output: tektonconfig.operator.tekton.dev/config patched [runner: 1] * Assert pipelines are "present" in "openshift" namespace 2024/04/29 07:45:33 Verifying that 27 pipelines are present in namespace openshift [runner: 2] * Assert pruner cronjob(s) in namespace "target namespace" contains "1" number of container(s) 2024/04/29 07:45:35 Verifying if the cronjob with prefix tekton-resource-pruner in namespace openshift-pipelines contains 1 number of containers 2024/04/29 07:45:35 1 containers found in the cronjob spec [runner: 2] * Delete project "test-project-1" 2024/04/29 07:45:35 Deleting project test-project-1 2024/04/29 07:45:38 Verifying that 27 pipelines are present in namespace openshift 2024/04/29 07:45:38 Pipelines are present in namespace openshift 2024/04/29 07:45:42 output: project.project.openshift.io "test-project-1" deleted [runner: 2] * Delete project "test-project-2" 2024/04/29 07:45:42 Deleting project test-project-2 2024/04/29 07:45:45 output: project.project.openshift.io "releasetest-d84vj" deleted [runner: 1] Sending kill message to runner. ok command-line-arguments 366.777s Runner with PID:30551 has exited 2024/04/29 07:45:49 output: project.project.openshift.io "test-project-2" deleted [runner: 2] * Remove auto pruner configuration from config CR 2024/04/29 07:45:49 Removing pruner configuration from config CR 2024/04/29 07:45:57 output: project.project.openshift.io "releasetest-xz654" deleted [runner: 2] ## Verify that the operator is up and running after deleting namespace with pruner annotation: PIPELINES-12-TC15 2024/04/29 07:45:57 output: Now using project "releasetest-xscdl" on server "https://api.ci-op-bfkt0dtt-c64b7.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 [runner: 2] * Validate Operator should be installed [runner: 2] * Verify ServiceAccount "pipeline" exist 2024/04/29 07:45:57 Verify SA "pipeline" is created in namespace "releasetest-xscdl" [runner: 2] * Remove auto pruner configuration from config CR 2024/04/29 07:46:02 Removing pruner configuration from config CR [runner: 2] * Assert if cronjob with prefix "tekton-resource-pruner" is "not present" in target namespace 2024/04/29 07:46:02 Verifying if the cronjob tekton-resource-pruner is not present in namespace openshift-pipelines 2024/04/29 07:46:07 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:46:07 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines [runner: 2] * Create |S.NO|resource_dir | |----|---------------------------------------------| |1 |testdata/pruner/namespaces/namespace-one.yaml| 2024/04/29 07:46:08 output: namespace/namespace-one created [runner: 2] * Assert if cronjob with prefix "tekton-resource-pruner" is "present" in target namespace 2024/04/29 07:46:08 Verifying if the cronjob tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:46:13 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:46:13 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines [runner: 2] * Delete project "namespace-one" 2024/04/29 07:46:13 Deleting project namespace-one 2024/04/29 07:46:19 output: project.project.openshift.io "namespace-one" deleted [runner: 2] * Sleep for "5" seconds 2024/04/29 07:46:19 Sleeping for 5 seconds [runner: 2] * Assert if cronjob with prefix "tekton-resource-pruner" is "not present" in target namespace 2024/04/29 07:46:24 Verifying if the cronjob tekton-resource-pruner is not present in namespace openshift-pipelines 2024/04/29 07:46:29 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:46:29 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines [runner: 2] * Validate Operator should be installed [runner: 2] * Create |S.NO|resource_dir | |----|---------------------------------------------| |1 |testdata/pruner/namespaces/namespace-two.yaml| 2024/04/29 07:46:30 output: namespace/namespace-two created [runner: 2] * Assert if cronjob with prefix "tekton-resource-pruner" is "present" in target namespace 2024/04/29 07:46:30 Verifying if the cronjob tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:46:35 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:46:35 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines [runner: 2] * Delete project "namespace-two" 2024/04/29 07:46:35 Deleting project namespace-two 2024/04/29 07:46:42 output: project.project.openshift.io "namespace-two" deleted [runner: 2] * Sleep for "5" seconds 2024/04/29 07:46:42 Sleeping for 5 seconds [runner: 2] * Assert if cronjob with prefix "tekton-resource-pruner" is "not present" in target namespace 2024/04/29 07:46:47 Verifying if the cronjob tekton-resource-pruner is not present in namespace openshift-pipelines 2024/04/29 07:46:52 Verifying if cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:46:52 Cronjob with prefix tekton-resource-pruner is present in namespace openshift-pipelines 2024/04/29 07:46:59 output: project.project.openshift.io "releasetest-xscdl" deleted 2024/04/29 07:46:59 output: tektonconfig.operator.tekton.dev/config patched [runner: 2] Sending kill message to runner. ok command-line-arguments 435.243s Runner with PID:31000 has exited Transformed SuiteResult to report structure Successfully generated html-report to => /logs/artifacts/html-report/2024-04-29_07.46.59/index.html Done generating HTML report using theme from /tmp/plugins/html-report/4.3.1/themes/default Successfully generated xml-report to => /logs/artifacts/xml-report/2024-04-29 07.46.59 Sending kill message to Html Report plugin. Sending kill message to Xml Report plugin. Specifications: 2 executed 2 passed 0 failed 0 skipped Scenarios: 8 executed 8 passed 0 failed 0 skipped Total time taken: 7m20.552s 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 xml-report is already installed. Plugin go is already installed. Plugin html-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: 44411 Successfully made the connection with plugin with port: 44411 Starting Xml Report plugin Attempting to connect to grpc server at port: 34685 Successfully made the connection with plugin with port: 34685 Initialising suite data store. # Verify RBAC Resources  ## Disable RBAC resource creation: PIPELINES-11-TC01 2024/04/29 07:47:04 output: Now using project "releasetest-958wv" on server "https://api.ci-op-bfkt0dtt-c64b7.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 2024/04/29 07:47:05 Waiting for operator to be up and running.... 2024/04/29 07:47:05 Operator is up  * Validate Operator should be installed ...[PASS] 2024/04/29 07:47:05 enable auto creation of RBAC resources 2024/04/29 07:47:05 output: tektonconfig.operator.tekton.dev/config patched (no change)  * Update TektonConfig CR to use param with name createRbacResource and value "true" to "enable" auto creation of RBAC resources ...[PASS] 2024/04/29 07:47:05 Verifying that TektonConfig status is "installed" 2024/04/29 07:47:05 Waiting for config cr InstalledStatus Actual: [False] Expected: [True] 2024/04/29 07:47:15 Verifying that service account pipeline exists 2024/04/29 07:47:20 Verifying that cluster role pipelines-scc-clusterrole exists 2024/04/29 07:47:25 Verifying that config map config-service-cabundle exists 2024/04/29 07:47:30 Verifying that config map config-trusted-cabundle exists 2024/04/29 07:47:35 Verifying that role binding openshift-pipelines-edit exists 2024/04/29 07:47:40 Verifying that role binding pipelines-scc-rolebinding exists 2024/04/29 07:47:45 Verifying that security context constraint pipelines-scc exists  * Verify RBAC resources are auto created successfully ...[PASS] 2024/04/29 07:47:45 disable auto creation of RBAC resources 2024/04/29 07:47:45 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] 2024/04/29 07:47:50 Verifying that service account pipeline exists 2024/04/29 07:47:55 Verifying that cluster role pipelines-scc-clusterrole doesn't exist 2024/04/29 07:48:00 Verifying that config map config-service-cabundle doesn't exist 2024/04/29 07:48:05 Verifying that config map config-trusted-cabundle doesn't exist 2024/04/29 07:48:10 Verifying that role binding edit doesn't exist 2024/04/29 07:48:15 Verifying that role binding pipelines-scc-rolebinding doesn't exist 2024/04/29 07:48:20 Verifying that security context constraint pipelines-scc doesn't exist  * Verify RBAC resources disabled successfully ...[PASS] 2024/04/29 07:48:20 enable auto creation of RBAC resources 2024/04/29 07:48:21 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] 2024/04/29 07:48:21 Verifying that TektonConfig status is "installed" 2024/04/29 07:48:26 Verifying that service account pipeline exists 2024/04/29 07:48:31 Verifying that cluster role pipelines-scc-clusterrole exists 2024/04/29 07:48:36 Verifying that config map config-service-cabundle exists 2024/04/29 07:48:41 Verifying that config map config-trusted-cabundle exists 2024/04/29 07:48:46 Verifying that role binding openshift-pipelines-edit exists 2024/04/29 07:48:51 Verifying that role binding pipelines-scc-rolebinding exists 2024/04/29 07:48:56 Verifying that security context constraint pipelines-scc exists  * Verify RBAC resources are auto created successfully ...[PASS] 2024/04/29 07:49:03 output: project.project.openshift.io "releasetest-958wv" deleted Transformed SuiteResult to report structure Successfully generated html-report to => /logs/artifacts/html-report/2024-04-29_07.49.03/index.html Done generating HTML report using theme from /tmp/plugins/html-report/4.3.1/themes/default Successfully generated xml-report to => /logs/artifacts/xml-report/2024-04-29 07.49.03 Sending kill message to Html Report plugin. Sending kill message to Xml Report plugin. Sending kill message to runner. ok command-line-arguments 118.966s Runner with PID:32728 has exited Specifications: 1 executed 1 passed 0 failed 0 skipped Scenarios: 1 executed 1 passed 0 failed 0 skipped Total time taken: 1m58.901s Updates are available. Run `gauge update -c` for more info. Rename xml files to junit_test_*.xml