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

List of default Camel K event sources disappears when adding a custom event source

XMLWordPrintable

    • No
    • ODC Sprint 3263, ODC Sprint 3264
    • 2
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required
    • Done

      This is a clone of issue OCPBUGS-41905. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-39110. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-29528. The following is the description of the original issue:

      Description of problem:

      Camel K provides a list of Kamelets that are able to act as an event source or sink for a Knative eventing message broker.
      
      Usually the list of Kamelets installed with the Camel K operator are displayed in the Developer Catalog list of available event sources with the provider "Apache Software Foundation" or "Red Hat Integration".
      
      When a user adds a custom Kamelet custom resource to the user namespace the list of default Kamelets coming from the Camel K operator is gone. The Developer Catalog event source list then only displays the custom Kamelet but not the default ones.

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

          

      How reproducible:

      Apply a custom Kamelet custom resource to the user namespace and open the list of available event sources in Dev Console Developer Catalog.

      Steps to Reproduce:

          1. install global Camel K operator in operator namespace (e.g. openshift-operators)
          2. list all available event sources in "default" user namespace and see all Kamelets listed as event sources/sinks
          3. add a custom Kamelet custom resource to the default namespace
          4. see the list of available event sources only listing the custom Kamelet and the default Kamelets are gone from that list
          

      Actual results:

      Default Kamelets that act as event source/sink are only displayed in the Developer Catalog when there is no custom Kamelet added to a namespace.    

      Expected results:

      Default Kamelets coming with the Camel K operator (installed in the operator namespace) should always be part of the Developer Catalog list of available event sources/sinks. When the user adds more custom Kamelets these should be listed, too.   

      Additional info:

      Reproduced with Camel K operator 2.2 and OCP 4.14.8

      screenshots: https://drive.google.com/drive/folders/1mTpr1IrASMT76mWjnOGuexFr9-mP0y3i?usp=drive_link

       

              rh-ee-lprabhu Lokananda Prabhu
              openshift-crt-jira-prow OpenShift Prow Bot
              Sanket Pathak Sanket Pathak
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: