WebUI Error after Trigger Creation about pipelines-tutorial

[meanderix]

I'm seeing exactly the same error. After installing the tutorial I get a WSOD in the WebUI when clicking "pipelines". I'm still able to access /triggers and /tasks and it looks like the pipelinerun executes correctly (a functional instance of vote-ui is deployed).

[meanderix]

I managed to get a more detailed traces from /k8s/ns/pipelines-tutorial/triggers.tekton.dev~v1alpha1~EventListener/vote-app:

Component trace:

in Unknown
    in div
    in div
    in div
    in Unknown
    in t
    in t
    in div
    in Data
    in StatusBox
    in div
    in Unknown
    in Unknown
    in Unknown
    in Unknown
    in O
    in Unknown
    in O
    in Unknown
    in o
    in DetailsPage
    in Unknown
    in l
    in Unknown
    in O
    in t
    in t
    in div
    in div
    in section
    in PageSection
    in Unknown
    in O
    in div
    in div
    in DrawerMain
    in DrawerContent
    in div
    in Drawer
    in NotificationDrawer
    in Unknown
    in O
    in main
    in div
    in Page
    in div
    in DrawerContentBody
    in div
    in div
    in DrawerMain
    in DrawerContent
    in div
    in Drawer
    in Unknown
    in O
    in I
    in l
    in O
    in Unknown
    in O
    in t
    in t
    in t
    in t

Stack trace:

TypeError: Cannot read property 'name' of undefined
    at https://console-openshift-console.apps.k8s.gu.se/static/eventlistener-details-chunk-519f3e48aba2047fadf7.min.js:1:17442
    at Array.map (<anonymous>)
    at t.a (https://console-openshift-console.apps.k8s.gu.se/static/eventlistener-details-chunk-519f3e48aba2047fadf7.min.js:1:17361)
    at No (https://console-openshift-console.apps.k8s.gu.se/static/vendors~main-chunk-3c658109a04f0e334208.min.js:160:55337)
    at Ks (https://console-openshift-console.apps.k8s.gu.se/static/vendors~main-chunk-3c658109a04f0e334208.min.js:160:98261)
    at Bs (https://console-openshift-console.apps.k8s.gu.se/static/vendors~main-chunk-3c658109a04f0e334208.min.js:160:84008)
    at Fs (https://console-openshift-console.apps.k8s.gu.se/static/vendors~main-chunk-3c658109a04f0e334208.min.js:160:81035)
    at Ms (https://console-openshift-console.apps.k8s.gu.se/static/vendors~main-chunk-3c658109a04f0e334208.min.js:160:79608)
    at https://console-openshift-console.apps.k8s.gu.se/static/vendors~main-chunk-3c658109a04f0e334208.min.js:160:41759
    at t.unstable_runWithPriority (https://console-openshift-console.apps.k8s.gu.se/static/vendors~main-chunk-3c658109a04f0e334208.min.js:168:3878)

[meanderix]

Problem seem to be resolved by reverting the event listener from "tech preview 3" to "tech preview 2":
https://github.com/openshift/pipelines-tutorial/blob/release-tech-preview-3/03_triggers/04_event_listener.yaml
https://github.com/openshift/pipelines-tutorial/blob/release-tech-preview-2/03_triggers/03_event_listener.yaml

I had some other issues when deploying the event listener from "tech preview 2" (which is why i tried to update to the latest one):
Error: admission webhook "validation.webhook.triggers.tekton.dev" denied the request: validation failed: expected exactly one, got neither: spec.triggers[0].bindings[0].Ref, spec.triggers[0].bindings[0].Spec
and
Error: failed to create resource: admission webhook "webhook.triggers.tekton.dev" denied the request: mutation failed: cannot decode incoming new object: json: unknown field "ref"
I don't see these errors when manually editing the yaml in the WebUI.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.