Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-16068

Kamelets are looked up in github/apache/camel-kamelets in global installation mode with OLM=true

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: Camel-K-GA, 2021-M2
    • Fix Version/s: Camel-K-GA
    • Component/s: Camel-K
    • Labels:
      None

      Description

      The kamelet lookup path seems to contain repository github/apache/camel-kamelets in case of global mode Camel-K installation via OLM.
      Apache/camel-kamelets github repository should be disabled in the product (info from @nferraro) but it is not.

      I tried to run test e2e/common/global_kamelet_test.go (repo http://code.engineering.redhat.com/gerrit/jboss-fuse/camel-k, branch 1.3.0.fuse-800003-redhat-00002), with following setup:

      KAMEL_INSTALL_OLM=true
      KAMEL_INSTALL_OLM_SOURCE=camel-k-source 
      KAMEL_BIN=linux-client-1.3.0.fuse-800003-redhat-00002/kamel
      

      (on lab OCP 4.7 is installed build M4 2.2 as CatalogSource with name camel-k-source)

      Prior to test run, Camel-K operator isn't installed on the server, also

      $ oc get pods -n openshift-operators
      No resources found in openshift-operators namespace.
      
      $ go test -timeout 10m -v -tags=integration ./e2e/common/global_kamelet_test.go
      === RUN   TestRunGlobalKamelet
      Using external kamel binary on path linux-client-1.3.0.fuse-800003-redhat-00002/kamel
      OLM is available in the cluster
      Camel K installed in namespace <ns> via OLM subscription (global mode)
      Using external kamel binary on path linux-client-1.3.0.fuse-800003-redhat-00002/kamel
      Camel K operator installation skipped
      Camel K installed in namespace <ns2> 
      Using external kamel binary on path linux-client-1.3.0.fuse-800003-redhat-00002/kamel
      integration "timer-kamelet-usage" created
      

      Test created camel-k-operator pod in openshift-operators namespace; the integration timer-kamelet-usage looks for kamelet in following path:

      $ oc describe it timer-kamelet-usage -n <ns2>
        Type     Reason            Age                From                            Message
        ----     ------            ----               ----                            -------
        Warning  IntegrationError  0s (x12 over 18s)  camel-k-integration-controller  Cannot reconcile Integration timer-kamelet-usage: error during trait customization: kamelet my-own-timer-source not found in any of the defined repositories: (Kubernetes[namespace=<ns2>], Kubernetes[namespace=openshift-operators], Github[owner=apache, repo=camel-kamelets, path=, ref=])
      

      However, the the apache/camel-kamelets github repository should be disabled in the product (info from @nferraro).

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            lfabriko Lucie Krejcirova
            Tester:
            Lucie Krejcirova Lucie Krejcirova
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: