Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Oddity in channel name #2468

Closed
pilhuhn opened this issue Jun 30, 2021 · 5 comments · Fixed by #2476
Closed

Oddity in channel name #2468

pilhuhn opened this issue Jun 30, 2021 · 5 comments · Fixed by #2476
Labels
area/knative Related to Knative

Comments

@pilhuhn
Copy link

pilhuhn commented Jun 30, 2021

I have this route definition https://gist.github.com/pilhuhn/97cf0bfaec2d3d5a78ccaa13ee31581f and when doing kamel run I get the following error:
I am pulling in the dependency via jitpack

[1] 2021-06-30 07:06:24,289 ERROR [io.qua.run.Application] (main) Failed to start application (with profile prod): java.lang.IllegalArgumentException: Unable to find a resource definition for channel/sink/return-channel

Notice the sink part, that I did not put in.

When I try the following

- from:
    uri: "timer:clock?period=3000"
    steps:
      - set-body:
          constant: "Hello World from Camel K"
      - to:
          uri: "knative:channel/return-channel"
      - log:
          message: "Send message"

and deploy it, I do not get the error, even if the to/uri is the same

@astefanutti astefanutti added the area/knative Related to Knative label Jun 30, 2021
@nicolaferraro
Copy link
Member

Hi @pilhuhn can you give more information about the environment?
Iirc, when a single sink is present, Camel K tries to use Knative sinkbinding. So you should be able to find it when running kubectl get sinkbindings.

Can you provide the output of kamel dump on the namespace, or specifically kubectl get pod -l camel.apache.org/integration -o yaml. I'm wondering if the binding has been applied correctly.

Also what versions are you using for Camel K and Knative?

@pilhuhn
Copy link
Author

pilhuhn commented Jul 1, 2021

@nicolaferraro I'll assemble the information in a minute. What puzzles me is that the example in the gist fails, while the pasted one works, even if they both have the same -to uri: entry.

@pilhuhn
Copy link
Author

pilhuhn commented Jul 1, 2021

 % oc get sinkbindings
NAME                           SINK                                                                      AGE   READY   REASON
notifications-gw-sinkbinding   http://broker-ingress.knative-eventing.svc.cluster.local/hrupp/mybroker   10d   True
% oc get channels
NAME             URL                                                        AGE   READY   REASON
return-channel   http://return-channel-kn-channel.hrupp.svc.cluster.local   42h   True

Camel-K 1.4

@pilhuhn
Copy link
Author

pilhuhn commented Jul 1, 2021

% kamel get
NAME	PHASE	KIT
c-tower	Running	hrupp/kit-c3ddgss5jcbbdo9jij8g
% kn service list
NAME            URL                                                                 LATEST                AGE     CONDITIONS   READY   REASON
c-tower         http://c-tower-hrupp.apps.integrations.w3us.s1.devshift.org                               25h     0 OK / 3     False   RevisionMissing : Configuration "c-tower" does not have any ready Revision.
 % kn revision list c-tower-00001
NAME            SERVICE   TRAFFIC   TAGS   GENERATION   AGE   CONDITIONS   READY   REASON
c-tower-00001   c-tower                    1            25h   0 OK / 4     False   ProgressDeadlineExceeded : Initial scale was n ...

@pilhuhn
Copy link
Author

pilhuhn commented Jul 1, 2021

( Talked with Nicola ) That is apparently an issue in the operator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/knative Related to Knative
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants