You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is repeated as many times as we have Kamelets from default catalog, so, I have the feeling it relates to the change we did either in apache/camel-kamelets#754 or apache/camel-kamelets#755. Likely there is something not good when we try to install the kamelets with .template instead that .flow
The text was updated successfully, but these errors were encountered:
$ export KAMELET_CATALOG_DIR="/tmp/"
$ kamel install
OLM is not available in the cluster. Fallback to regular installation.
Camel K installed in namespace default
$ k get pods
NAME READY STATUS RESTARTS AGE
camel-k-operator-7c96b9b6bd-x8b6c 1/1 Running 9 (16m ago) 32m
You can use any existing directory which has no kamelets defined in it
I think the problem was due to some old kamelet definition in my namespace. If I delete the kamelets, then the installation procedure won't show that problem.
Note:
The error fatal error: sync: unlock of unlocked mutex concerns the use of sync.Once in the kamelet loading code. Documentation recommends that sync.Once should not be re-assigned within the function that is being executed. This error is the result.
See #3063 and related PRs for modification of code to ameliorate this problem.
I am trying to install in my local
minikube
usingkamel
version1.8.0
. The operator pod starts but suddenly breaks with following traces:This is repeated as many times as we have Kamelets from default catalog, so, I have the feeling it relates to the change we did either in apache/camel-kamelets#754 or apache/camel-kamelets#755. Likely there is something not good when we try to install the kamelets with
.template
instead that.flow
The text was updated successfully, but these errors were encountered: