You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "timothydilbert (via GitHub)" <gi...@apache.org> on 2023/03/13 13:46:34 UTC
[GitHub] [camel-k] timothydilbert opened a new issue, #4129: All KameletBindings reporting "Integration X does not have a readiness condition" error message
timothydilbert opened a new issue, #4129:
URL: https://github.com/apache/camel-k/issues/4129
When deploying a KameletBinding in an OpenShift cluster, we're getting the following error message:
```
Integration "integration-name" does not have a readiness condition
```
**Steps to reproduce:**
1. Go to _Administrator_ > _Operators_ > _Installed Operators_ > _Camel K Operator_ > _KameletBinding_
2. Click _Create KameletBinding_ then click _Save_ (without edits)
3. After a few minutes, the integration fails to deploy with Status `Phase: Error` and the following YAML
```yaml
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
creationTimestamp: '2023-03-13T13:34:06Z'
generation: 1
managedFields:
- apiVersion: camel.apache.org/v1alpha1
fieldsType: FieldsV1
fieldsV1:
'f:spec':
.: {}
'f:sink':
.: {}
'f:ref':
.: {}
'f:apiVersion': {}
'f:kind': {}
'f:name': {}
'f:source':
.: {}
'f:properties':
.: {}
'f:message': {}
'f:ref':
.: {}
'f:apiVersion': {}
'f:kind': {}
'f:name': {}
manager: Mozilla
operation: Update
time: '2023-03-13T13:34:06Z'
- apiVersion: camel.apache.org/v1alpha1
fieldsType: FieldsV1
fieldsV1:
'f:status':
.: {}
'f:conditions': {}
'f:observedGeneration': {}
'f:phase': {}
manager: kamel
operation: Update
subresource: status
time: '2023-03-13T13:36:58Z'
name: example-v2
namespace: openshift-operators
resourceVersion: '6623300'
uid: df236b47-3841-45ea-8bf1-c87d7b51be4e
spec:
sink:
ref:
apiVersion: messaging.knative.dev/v1
kind: InMemoryChannel
name: example
source:
properties:
message: Hello world
ref:
apiVersion: camel.apache.org/v1alpha1
kind: Kamelet
name: example
status:
conditions:
- lastTransitionTime: '2023-03-13T13:36:58Z'
lastUpdateTime: '2023-03-13T13:36:58Z'
message: Integration "example-v2" does not have a readiness condition
status: Unknown
type: Ready
observedGeneration: 1
phase: Error
```
**Kubernetes Cluster:**
OpenShift 4.12.5
**Operator:**:
Camel K Operator and the Red Hat Integration - Camel K Operator (tried both, and they both fail with the same message.
**CLI Version:**
Camel K Client 1.12.0
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] timothydilbert commented on issue #4129: All KameletBindings reporting "Integration X does not have a readiness condition" error message
Posted by "timothydilbert (via GitHub)" <gi...@apache.org>.
timothydilbert commented on issue #4129:
URL: https://github.com/apache/camel-k/issues/4129#issuecomment-1466590291
Figured out the issue. I'm embarrassed to admit that the OpenShift internal registry was not configured.
I think it would be useful to introduce logic in Camel-K during deployment/installation to check for the image registry and throw an error if it isn't configured. Shall I create a separate Issue for this?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #4129: All KameletBindings reporting "Integration X does not have a readiness condition" error message
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #4129:
URL: https://github.com/apache/camel-k/issues/4129#issuecomment-1466443625
> ```
> {"level":"info","ts":1678721314.489918,"logger":"camel-k.controller.kameletbinding","msg":"Invoking action monitor","request-namespace":"openshift-operators","request-name":"timer-to-log","api-version":"camel.apache.org/v1alpha1","kind":"KameletBinding","ns":"openshift-operators","name":"timer-to-log"}
> {"level":"info","ts":1678721314.4919193,"logger":"camel-k","msg":"could not find any knative type in namespace openshift-operators, last error was: the server could not find the requested resource"}
> ```
Not a bug, some misleading information: https://github.com/apache/camel-k/issues/2397
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #4129: All KameletBindings reporting "Integration X does not have a readiness condition" error message
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #4129:
URL: https://github.com/apache/camel-k/issues/4129#issuecomment-1466615425
Yes please. Close this one and feel free to create any further enhancement request.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] christophd commented on issue #4129: All KameletBindings reporting "Integration X does not have a readiness condition" error message
Posted by "christophd (via GitHub)" <gi...@apache.org>.
christophd commented on issue #4129:
URL: https://github.com/apache/camel-k/issues/4129#issuecomment-1466472206
can you see any IntegrationKit resources in the operator namespace?
```shell
oc get ik
```
What does it say? Same for Build resources. You can have a look at these resources to also get some error information.
Maybe it is good idea to remove all IntegrationKit and Build resources that you can see in order to start fresh
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] timothydilbert commented on issue #4129: All KameletBindings reporting "Integration X does not have a readiness condition" error message
Posted by "timothydilbert (via GitHub)" <gi...@apache.org>.
timothydilbert commented on issue #4129:
URL: https://github.com/apache/camel-k/issues/4129#issuecomment-1466369535
It's strange because I am getting a completely different behaviour when I try to deploy the example YAML you provided.
Basically, I am getting the same error message shown in my original issue description. And, the following logs are showing up under the operator container:
```
{"level":"info","ts":1678721314.489918,"logger":"camel-k.controller.kameletbinding","msg":"Invoking action monitor","request-namespace":"openshift-operators","request-name":"timer-to-log","api-version":"camel.apache.org/v1alpha1","kind":"KameletBinding","ns":"openshift-operators","name":"timer-to-log"}
{"level":"info","ts":1678721314.4919193,"logger":"camel-k","msg":"could not find any knative type in namespace openshift-operators, last error was: the server could not find the requested resource"}
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] timothydilbert commented on issue #4129: All KameletBindings reporting "Integration X does not have a readiness condition" error message
Posted by "timothydilbert (via GitHub)" <gi...@apache.org>.
timothydilbert commented on issue #4129:
URL: https://github.com/apache/camel-k/issues/4129#issuecomment-1466633417
Further enhancement request submitted via #4130
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] timothydilbert commented on issue #4129: All KameletBindings reporting "Integration X does not have a readiness condition" error message
Posted by "timothydilbert (via GitHub)" <gi...@apache.org>.
timothydilbert commented on issue #4129:
URL: https://github.com/apache/camel-k/issues/4129#issuecomment-1466454349
Hi @squakez
I also saw #2397 so started to rule it out as a culprit. What's left to troubleshoot?
In case this helps, below is the Event stream from the KameletBinding:
```
13 Mar 2023, 10:21 Condition "Ready" is "False" for KameletBinding timer-to-log: Integration "timer-to-log" is in "Creating" phase
13 Mar 2023, 10:21 KameletBinding "timer-to-log" in phase "Creating"
13 Mar 2023, 10:24 KameletBinding "timer-to-log" in phase "Error"
13 Mar 2023, 10:24 Condition "Ready" is "Unknown" for KameletBinding timer-to-log: Integration "timer-to-log" does not have a readiness condition
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] timothydilbert closed issue #4129: All KameletBindings reporting "Integration X does not have a readiness condition" error message
Posted by "timothydilbert (via GitHub)" <gi...@apache.org>.
timothydilbert closed issue #4129: All KameletBindings reporting "Integration X does not have a readiness condition" error message
URL: https://github.com/apache/camel-k/issues/4129
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] christophd commented on issue #4129: All KameletBindings reporting "Integration X does not have a readiness condition" error message
Posted by "christophd (via GitHub)" <gi...@apache.org>.
christophd commented on issue #4129:
URL: https://github.com/apache/camel-k/issues/4129#issuecomment-1466349328
The KameletBinding is not able to run because the referenced Kamelet source(`example`) does not exist. You need to reference a Kamelet that is available from one of the Kamelet catalogs (e.g. https://camel.apache.org/camel-kamelets/3.20.x/). Also the binding uses a Knative InMemoryChannel `example` as a sink so you would have to make sure to create this channel before running the binding.
Here is a KameletBinding I just verified on OCP 4.12 with Camel K 1.12.0
```yaml
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
labels:
app: camel-k
name: timer-to-log
spec:
source:
ref:
apiVersion: camel.apache.org/v1alpha1
name: timer-source
kind: Kamelet
properties:
message: Hello world
sink:
ref:
apiVersion: camel.apache.org/v1alpha1
name: log-sink
kind: Kamelet
```
The binding log output:
```
2023-03-13 15:09:30,848 INFO [org.apa.cam.k.Runtime] (main) Apache Camel K Runtime 1.17.0
2023-03-13 15:09:30,874 INFO [org.apa.cam.qua.cor.CamelBootstrapRecorder] (main) Bootstrap runtime: org.apache.camel.quarkus.main.CamelMainRuntime
2023-03-13 15:09:30,877 INFO [org.apa.cam.mai.MainSupport] (main) Apache Camel (Main) 3.20.1 is starting
2023-03-13 15:09:31,034 INFO [org.apa.cam.k.lis.SourcesConfigurer] (main) Loading routes from: SourceDefinition{name='camel-k-embedded-flow', language='yaml', type='source', location='file:/etc/camel/sources/camel-k-embedded-flow.yaml', }
2023-03-13 15:09:31,130 INFO [org.apa.cam.k.lis.SourcesConfigurer] (main) Loading routes from: SourceDefinition{name='log-sink', language='yaml', type='source', location='file:/etc/camel/sources/log-sink.yaml', }
2023-03-13 15:09:31,134 INFO [org.apa.cam.k.lis.SourcesConfigurer] (main) Loading routes from: SourceDefinition{name='timer-source', language='yaml', type='source', location='file:/etc/camel/sources/timer-source.yaml', }
2023-03-13 15:09:31,643 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Apache Camel 3.20.1 (camel-1) is starting
2023-03-13 15:09:31,660 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Routes startup (started:3)
2023-03-13 15:09:31,661 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Started binding (kamelet://timer-source/source)
2023-03-13 15:09:31,661 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Started source (timer://tick)
2023-03-13 15:09:31,661 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Started sink (kamelet://source)
2023-03-13 15:09:31,661 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Apache Camel 3.20.1 (camel-1) started in 221ms (build:0ms init:203ms start:18ms)
2023-03-13 15:09:31,666 INFO [io.quarkus] (main) camel-k-integration 1.12.0 on JVM (powered by Quarkus 2.16.0.Final) started in 4.319s.
2023-03-13 15:09:31,667 INFO [io.quarkus] (main) Profile prod activated.
2023-03-13 15:09:31,667 INFO [io.quarkus] (main) Installed features: [camel-bean, camel-core, camel-k-core, camel-k-runtime, camel-kamelet, camel-kubernetes, camel-log, camel-timer, camel-yaml-dsl, cdi, kubernetes-client, security]
2023-03-13 15:09:32,671 INFO [log-sink] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world]
2023-03-13 15:09:33,659 INFO [log-sink] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world]
2023-03-13 15:09:34,659 INFO [log-sink] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world]
2023-03-13 15:09:35,659 INFO [log-sink] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world]
2023-03-13 15:09:36,659 INFO [log-sink] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world]
2023-03-13 15:09:37,660 INFO [log-sink] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world]
2023-03-13 15:09:38,660 INFO [log-sink] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world]
2023-03-13 15:09:39,660 INFO [log-sink] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world]
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org