Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-61140

Knative Eventing Broker content rendering does not filter by the ownership of triggers

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.19
    • Management Console
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

          When you have multiple brokers in a namespace, clicking on any of them renders *all* the triggers in the namespace, regardless of whether they are assigned to the broker. In the case of removing a broker, the remaining triggers assigned to that broker are still listed in the other brokers content; you can click on them and then click on a link to a non-existent broker (404)

      Version-Release number of selected component (if applicable):

          

      How reproducible:

          Always

      Steps to Reproduce:

          1. Create two brokers in the namespace with different names
          2. Create one trigger that is assigned to one broker
          3. Create a second trigger that is assigned to the other broker
          4. Delete one of the brokers
          5. Use the topology to navigate to the broker; click on it, all triggers will be rendered
          6. Click on the trigger that was assigned to the deleted broker
          7. In the trigger content pane click on the name of the deleted broker
          

      Actual results:

      All triggers in the namespace are rendered as part of the broker content

      Expected results:

          Only triggers assigned to the broker should be rendered (and clickable) when the broker content pane is rendered

      Additional info:

          

              viraj-1 Vikram Raj
              utherp0 Ian Lawson
              None
              None
              YaDan Pei YaDan Pei
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: