subject:"\[I\] Error configuring property\: camel.component.test\[00001\]port\[80\]tcp.addr because cannot find component with name test\[00001\]port\[80\]tcp. \[camel\-k\]"



lburgazzoli commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1971850783

   yes I suspected about a bad env var injects somehow so glad we found the caue


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]

lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1971831095

@lburgazzoli After reaching to some people here, I found the root cause...

Kubernetes is injecting environment variables into any pod with metadata
based on the services that are running, as in:

```

APIM_CONNECTOR_C2228101_CF6A_4B3E_B502_62C99359A799_SERVICE_PORT=tcp://172.20.203.161:80

APIM_CONNECTOR_08BFC757_3D93_419A_8182_390B77D62DB1_SERVICE_PORT_80_TCP=tcp://172.20.206.40:80

APIM_CONNECTOR_08BFC757_3D93_419A_8182_390B77D62DB1_SERVICE_PORT_80_TCP_ADDR=172.20.206.40
```
That's not enough to explain the CAMEL_COMPONENT variables.
But then we found that a developer was also testing Camel components using
Camel K and created an integration named "camel-component-test".
This created a camel-component-test service that was active when the
operator started, and thus explains the weird env vars.

When I tested using the pod strategy it didn't fail because the the
camel-component-test service is no longer running.

So now everything is running fine again and I advised everyone about not
using camel-* names.

Thanks a lot for the guidance, @lburgazzoli.
I think we can close the ticket now and I'll remove the bug label.

--
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lburgazzoli commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1971778926

   O guess some of them could be marked as 'build time runtime fixed' by 
quakus, hence they may get persisted in the runner jar


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1971763622

   Bingo, we found it:
   
   ```
   I have no name!@camel-k-operator-74f8c76949-t5pgb:/$ env
   CAMEL_COMPONENT_TEST_2_PRIVATE_PORT_8022_TCP_PROTO=tcp
   
   (there are 300+ env vars here, most of them similar to the ones above)
   ```
   
   I don't see these variables in the deployment, so somehow k8s injected them. 
Let me show this to the person who created the cluster and installed Camel K.


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lburgazzoli commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1971731599

   can you also grab the env var of the operator ? 


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1971722356

   One interesting test:
   
   I cleared the integration kits, and created 2 copies of the same integration.
   One of them used the routine build strategy, the other one used pod build 
strategy.
   
   Only the one that used the routine strategy failed. I'll take a look at the 
jar files within the operator maven repo to try and file something wrong.
   


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1971677297

   I don't think so. Even in another namespace within the same cluster it 
works. I'm trying strategies like removing the build kits, cleaning the maven 
repo, restarting the node.
   It seems to be random, but might be triggered by adding or removing some jar 
file to the classpath depending on what components or traits I use. 


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lburgazzoli commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1971664486

   even more weird, is there a way to replicate it ?


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1971602776

   Here it is:
   
   ```
   root@demo008-1-deployment-7687bd4f74-792jk:/deployments# ls -R /etc/camel
   /etc/camel:
   application.properties  sources
   
   /etc/camel/sources:
   flow1.groovy
   
   
   root@demo008-1-deployment-7687bd4f74-792jk:/deployments# cat 
/etc/camel/application.properties 
   camel.k.sources[0].language = groovy
   camel.k.sources[0].location = file:/etc/camel/sources/flow1.groovy
   camel.k.sources[0].name = flow1
   
   root@demo008-1-deployment-7687bd4f74-792jk:/deployments# cat 
/etc/camel/sources/flow1.groovy 
   from('rest:GET:/hello1') 
.to("https://httpbin.org/delay/2?bridgeEndpoint=true";) .to("log:info")
   from('rest:GET:/hello2') .to("log:debug")
   ```


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lburgazzoli commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1971582375

   weird, are you also able to grab the content of the content of the files in 
/etc/camel ?


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1971564282

   I see. Well, I edited the generated deployment and replaced the java command 
with env. This is what I got:
   ```
   KUBERNETES_SERVICE_PORT=443
   KUBERNETES_PORT=tcp://172.20.0.1:443
   LANGUAGE=en_US:en
   CAMEL_K_MOUNT_PATH_SECRETS=/etc/camel/conf.d/_secrets
   CAMEL_K_CONF_D=/etc/camel/conf.d
   HOSTNAME=demo008-1-deployment-6c7685c768-9t7gw
   K_REVISION=demo008-1
   PORT=8080
   HOME=/root
   CAMEL_KNATIVE_CONFIGURATION={"services":[]}
   QUARKUS_LOG_CONSOLE_JSON=false
   CAMEL_K_OPERATOR_ID=camel-k
   JAVA_VERSION=jdk-17.0.10+7
   CAMEL_K_MOUNT_PATH_CONFIGMAPS=/etc/camel/conf.d/_configmaps
   K_CONFIGURATION=demo008
   CAMEL_K_VERSION=2.2.0
   KUBERNETES_PORT_443_TCP_ADDR=172.20.0.1
   
PATH=/opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
   KUBERNETES_PORT_443_TCP_PORT=443
   KUBERNETES_PORT_443_TCP_PROTO=tcp
   LANG=en_US.UTF-8
   CACERT_HOME=/opt/java/openjdk/lib/security
   K_SERVICE=demo008
   NAMESPACE=a1b2c3d4e5
   QUARKUS_LOG_LEVEL=INFO
   QUARKUS_CONSOLE_COLOR=true
   CAMEL_K_INTEGRATION=demo008
   KUBERNETES_SERVICE_PORT_HTTPS=443
   KUBERNETES_PORT_443_TCP=tcp://172.20.0.1:443
   JAVA_HOME=/opt/java/openjdk
   LC_ALL=en_US.UTF-8
   CAMEL_K_DIGEST=vEYn8Fws2XGenqr3LEJdkXrTlAI0ZjDQXw7lBBkY6bTI
   KUBERNETES_SERVICE_HOST=172.20.0.1
   PWD=/deployments
   CAMEL_K_CONF=/etc/camel/application.properties
   QUARKUS_LOG_CONSOLE_FORMAT=[%-5p][%d{-MM-dd HH:mm:ssZ}] %s%e%n
   CAMEL_K_RUNTIME_VERSION=3.2.3
   ```



-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lburgazzoli commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1971538992

   I need the actual env var of the pod as some env var are injected by k8s


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1971533594

   @lburgazzoli Isn't it the list in the spec included in the previous message?
   If you mean connect to the container and get the vars, I'm having trouble 
doing so, as the containes fails to start:
   
   ```
   k exec -it demo008-2-deployment-57447bf67-cpjsz -- c integration env
   Defaulted container "integration" out of: integration, queue-proxy
   error: unable to upgrade connection: container not found ("integration")
   ```
   



-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lburgazzoli commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1971512226

   can you get the env var of the running pod ?


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1971501937

   @lburgazzoli @squakez  Today it happened again and I managed to get the pod 
spec:
   ```
   apiVersion: v1
   kind: Pod
   metadata:
 annotations:
   autoscaling.knative.dev/minScale: "1"
   serving.knative.dev/creator: 
system:serviceaccount:a1b2c3d4e5:camel-k-operator
 labels:
   app: demo008-1
   camel.apache.org/integration: demo008
   pod-template-hash: 868fdc8467
   serving.knative.dev/configuration: demo008
   serving.knative.dev/configurationGeneration: "1"
   serving.knative.dev/configurationUID: 
bdc17079-0f8d-43a4-812b-89b83647af13
   serving.knative.dev/revision: demo008-1
   serving.knative.dev/revisionUID: a0b55f69-3b53-453f-8049-f6e121748192
   serving.knative.dev/service: demo008
   serving.knative.dev/serviceUID: a90dd895-2612-457c-8ae2-fd6e6bd6cfbe
 name: demo008-1-deployment-868fdc8467-5n4kz
 namespace: a1b2c3d4e5
   spec:
 containers:
 - args:
   - echo exec java -cp 
./resources:/etc/camel/application.properties:/etc/camel/conf.d/_resources:/etc/camel/resources:/etc/camel/sources/flow1.groovy:/etc/camel/sources/flow2.groovy:dependencies/app/camel-k-integration-2.2.0.jar:dependencies/lib/boot/io.github.crac.org-crac-0.1.3.jar:dependencies/lib/boot/io.quarkus.quarkus-bootstrap-runner-3.2.9.Final.jar:dependencies/lib/boot/io.quarkus.quarkus-development-mode-spi-3.2.9.Final.jar:dependencies/lib/boot/io.quarkus.quarkus-vertx-latebound-mdc-provider-3.2.9.Final.jar:dependencies/lib/boot/io.smallrye.common.smallrye-common-io-2.1.0.jar:dependencies/lib/boot/jakarta.json.jakarta.json-api-2.1.2.jar:dependencies/lib/boot/org.eclipse.parsson.parsson-1.1.2.jar:dependencies/lib/boot/org.graalvm.sdk.graal-sdk-23.0.1.jar:dependencies/lib/boot/org.jboss.logging.jboss-logging-3.5.1.Final.jar:dependencies/lib/boot/org.jboss.logmanager.jboss-logmanager-embedded-1.1.1.jar:dependencies/lib/boot/org.wildfly.common.wildfly-common-1.5.4.Final-f
 
ormat-001.jar:dependencies/lib/main/com.aayushatharva.brotli4j.brotli4j-1.12.0.jar:dependencies/lib/main/com.aayushatharva.brotli4j.native-linux-x86_64-1.12.0.jar:dependencies/lib/main/com.aayushatharva.brotli4j.service-1.12.0.jar:dependencies/lib/main/com.fasterxml.jackson.core.jackson-annotations-2.15.2.jar:dependencies/lib/main/com.fasterxml.jackson.core.jackson-core-2.15.2.jar:dependencies/lib/main/com.fasterxml.jackson.core.jackson-databind-2.15.2.jar:dependencies/lib/main/com.fasterxml.jackson.dataformat.jackson-dataformat-yaml-2.15.2.jar:dependencies/lib/main/com.fasterxml.jackson.datatype.jackson-datatype-jdk8-2.15.2.jar:dependencies/lib/main/com.fasterxml.jackson.datatype.jackson-datatype-jsr310-2.15.2.jar:dependencies/lib/main/com.fasterxml.jackson.module.jackson-module-parameter-names-2.15.2.jar:dependencies/lib/main/com.github.mifmif.generex-1.0.2.jar:dependencies/lib/main/commons-codec.commons-codec-1.16.0.jar:dependencies/lib/main/dk.brics.automaton.automaton-1.11-8.ja
 
r:dependencies/lib/main/io.fabric8.kubernetes-client-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-client-api-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-httpclient-vertx-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-admissionregistration-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-apiextensions-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-apps-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-autoscaling-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-batch-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-certificates-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-common-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-coordination-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-core-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-discovery-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-events-6.7.2.jar:dependencies/lib/main/io
 
.fabric8.kubernetes-model-extensions-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-flowcontrol-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-gatewayapi-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-metrics-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-networking-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-node-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-policy-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-rbac-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-resource-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-scheduling-6.7.2.jar:dependencies/lib/main/io.fabric8.kubernetes-model-storageclass-6.7.2.jar:dependencies/lib/main/io.fabric8.openshift-client-6.7.2.jar:dependencies/lib/main/io.fabric8.openshift-client-api-6.7.2.jar:dependencies/lib/main/io.fabric8.openshift-model-6.7.2.jar

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lburgazzoli commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1968974050

   Things like `private.service.port.http.usermetric` seems to be something 
injected i.e. by prometheus or whatnot and may be something that it is injected 
as en var. Camel does look also at the env var when trying to auto configure 
stuffs so it may be possible that some weird naming ends up being processed by 
camel as a property.
   
   So it would have been very useful to see the POD's env vars to confirm the 
hypothesis 
   


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1968931532

   @squakez I am using operator 2.2.0, camel-k-runtime 3.2.2.
   I could not find these values in any configuration either. I agree, it's 
really weird, specially considering that it was fixed after deleting and 
rebuilding the integration kits.
   
   @lburgazzoli I can't reproduce the issue anymore, but I compared the ksvc's 
with and without the knative trait enabled, and the only differences were the 
CAMEL_KNATIVE_CONFIGURATION environment var, with no services declared in it. 
And also the list of jar files used in the arguments.  


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lburgazzoli commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1968849221

   can you check the env vars available in the pod ? 


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



squakez commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1968688151

   Thanks for the detailed report. It is quite weird to see these 
configurations here: `camel.component.test[1]port=tcp://172.20.45.10:80`. 
What version of the operator were you running? Unless you're forcefully adding 
those configuration into your route/CLI execution, I cannot really understand 
where they are coming from. I mean, there's no operator logic entitled to do 
those changes. Maybe the camel-k-runtime is doing something strange, but, I've 
recently applied a refactoring to the code and I cannot recall anything 
similar. @lburgazzoli any idea of where those configuration may come from?


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]

2024-02-27 Thread via GitHub



lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1966343930

   After further investigation, I found out that another namespace in the same 
cluster that has Camel-K installed with the same configuration didn't reproduce 
the error.
   So, for testing, I decided do delete the integration kits from the failing 
namespace and reapplied the integration. And then it worked.
   
   So, at the end, I think I could not provide enough information to fix the 
issue, so maybe we might just close it.



-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1964620262

   If knative trait is disabled, the list of properties is shorter:
   ```
   2024-02-26 16:43:22,900 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
Properties from Camel properties component:
   2024-02-26 16:43:22,900 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.metrics.service.port.metrics=8080
   2024-02-26 16:43:22,900 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.metrics.port[8080]tcp.addr=172.20.253.1
   2024-02-26 16:43:22,900 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.mount.path.configmaps=/etc/camel/conf.d/_configmaps
   2024-02-26 16:43:22,901 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.integration=basic
   2024-02-26 16:43:22,901 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.sources[0].name=flow1
   2024-02-26 16:43:22,901 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.metrics.port[8080]tcp=tcp://172.20.253.1:8080
   2024-02-26 16:43:22,901 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.version=2.2.0
   2024-02-26 16:43:22,901 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.kubernetesConfig.clientEnabled=false
   2024-02-26 16:43:22,901 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.metrics.service.port=8080
   2024-02-26 16:43:22,901 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.metrics.port[8080]tcp.proto=tcp
   2024-02-26 16:43:22,901 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.conf=/etc/camel/application.properties
   2024-02-26 16:43:22,901 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.digest=vR4kTZd4vpDiwffwgyUmRWbb7fgbEboiC-nNvy5qvCYM
   2024-02-26 16:43:22,902 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.metrics.service.host=172.20.253.1
   2024-02-26 16:43:22,902 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.sources[0].location=file:/etc/camel/sources/flow1.groovy
   2024-02-26 16:43:22,902 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.metrics.port[8080]tcp.port=8080
   2024-02-26 16:43:22,902 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.runtime.version=3.2.3
   2024-02-26 16:43:22,902 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.mount.path.secrets=/etc/camel/conf.d/_secrets
   2024-02-26 16:43:22,902 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.conf.d=/etc/camel/conf.d
   2024-02-26 16:43:22,902 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.metrics.port=tcp://172.20.253.1:8080
   2024-02-26 16:43:22,902 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.operator.id=camel-k
   2024-02-26 16:43:22,903 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.sources[0].language=groovy
   ```
   


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1964595963

   Changed integration log level to TRACE in order to collect more information:
   ```
   2024-02-26 16:35:10,055 DEBUG [org.apa.cam.sup.ResolverHelper] (main) Found 
RoutesBuilderLoader: org.apache.camel.dsl.groovy.GroovyRoutesBuilderLoader via: 
META-INF/services/org/apache/camel/groovy
   2024-02-26 16:35:10,056 DEBUG [org.apa.cam.sup.ResolverHelper] (main) 
Detected and using RoutesBuilderLoader: 
org.apache.camel.dsl.groovy.GroovyRoutesBuilderLoader@6a6c7f42
   2024-02-26 16:35:10,100 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
Properties from Camel properties component:
   2024-02-26 16:35:10,101 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]port[80]tcp.addr=172.20.45.10
   2024-02-26 16:35:10,101 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.port[8022]tcp=tcp://172.20.102.234:8022
   2024-02-26 16:35:10,101 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.port[9090]tcp=tcp://172.20.102.234:9090
   2024-02-26 16:35:10,101 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]service.port.https=443
   2024-02-26 16:35:10,101 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.service.port.http.usermetric=9091
   2024-02-26 16:35:10,102 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]port[443]tcp.addr=172.20.45.10
   2024-02-26 16:35:10,102 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.integration=basic
   2024-02-26 16:35:10,102 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]port[443]tcp.proto=tcp
   2024-02-26 16:35:10,103 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.port[80]tcp.proto=tcp
   2024-02-26 16:35:10,103 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.port[8022]tcp.proto=tcp
   2024-02-26 16:35:10,103 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]service.port=80
   2024-02-26 16:35:10,103 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.port[443]tcp.proto=tcp
   2024-02-26 16:35:10,103 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.service.port.https=443
   2024-02-26 16:35:10,103 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.mount.path.secrets=/etc/camel/conf.d/_secrets
   2024-02-26 16:35:10,104 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.port[80]tcp=tcp://172.20.102.234:80
   2024-02-26 16:35:10,104 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.port[443]tcp=tcp://172.20.102.234:443
   2024-02-26 16:35:10,104 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.metrics.service.port.metrics=8080
   2024-02-26 16:35:10,104 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]service.host=172.20.45.10
   2024-02-26 16:35:10,104 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.service.port.http.autometric=9090
   2024-02-26 16:35:10,104 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.port[8012]tcp.proto=tcp
   2024-02-26 16:35:10,104 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]port[443]tcp=tcp://172.20.45.10:443
   2024-02-26 16:35:10,105 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.port[8012]tcp=tcp://172.20.102.234:8012
   2024-02-26 16:35:10,105 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.service.port.http.queueadm=8022
   2024-02-26 16:35:10,105 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.port[9090]tcp.addr=172.20.102.234
   2024-02-26 16:35:10,105 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.port[8012]tcp.addr=172.20.102.234
   2024-02-26 16:35:10,105 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.port[80]tcp.port=80
   2024-02-26 16:35:10,105 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.port[443]tcp.addr=172.20.102.234
   2024-02-26 16:35:10,105 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.port[9091]tcp.proto=tcp
   2024-02-26 16:35:10,106 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.component.test[1]private.port[9090]tcp.port=9090
   2024-02-26 16:35:10,106 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.metrics.port[8080]tcp.proto=tcp
   2024-02-26 16:35:10,106 DEBUG [org.apa.cam.mai.BaseMainSupport] (main) 
camel.k.conf=/etc/camel/application.properties
   2024-02-26 16:35:10,1

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1964354768

   In order to perform an isolated knative test, I exported the knative service 
created by the integration and modified it to create a new ksvc:
   - changed the image to ghcr.io/knative/helloworld-go:latest
   - removed the mounted volumes
   - removed the heatlh check probes
   The final result:
   ```
   apiVersion: serving.knative.dev/v1
   kind: Service
   metadata:
 annotations:
   serving.knative.dev/creator: kubernetes-admin
   serving.knative.dev/lastModifier: 
system:serviceaccount:a1b2c3d4e5:camel-k-operator
 labels:
   bindings.knative.dev/include: "true"
   camel.apache.org/generation: "1"
   camel.apache.org/integration: basic
 name: basic
 namespace: a1b2c3d4e5
   spec:
 template:
   metadata:
 annotations:
   autoscaling.knative.dev/minScale: "1"
 creationTimestamp: null
 labels:
   camel.apache.org/integration: basic
   spec:
 containerConcurrency: 0
 containers:
 - env:
   - name: TARGET
 value: "Go Sample v1"  
   image: ghcr.io/knative/helloworld-go:latest
   name: integration
 enableServiceLinks: false
 imagePullSecrets:
 - name: gcr-json-key
 timeoutSeconds: 300
 traffic:
 - latestRevision: true
   percent: 100
   ```
   
   This ksvc worked all 3 services were created.
   ```
   k get svc | grep basic
   basic ClusterIP   
None 80/TCP   
4m9s
   basic-1   ClusterIP   
172.20.70.17580/TCP,443/TCP   
4m10s
   basic-1-private   ClusterIP   
172.20.1.209 
80/TCP,443/TCP,9090/TCP,9091/TCP,8022/TCP,8012/TCP   4m10s
   ```
   Then I changed the ksvc and added a heath probe that would never succeed:
   ```
   readinessProbe:
 successThreshold: 1
 tcpSocket:
   port: 3000  
   ```
   And now I get the same situation where the pod fails, and the basic service 
is not created.
   
   So I think I can assume that the lack of one svc is actually a consequence, 
and not a cause of the pod failure.
   
   
   
   


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1964206985

   After further investigation into knative objects, I see the private endpoint 
was not assigned IP addresses:
   ```
   basic-1   
10.251.165.73:8012,10.251.165.73:8112   4m21s
   basic-1-private  
 4m21s
   ```
   And describing the private one shows me:
   ```
   Name: basic-1-private
   Namespace:a1b2c3d4e5
   Labels:   app=basic-1
 camel.apache.org/integration=basic
 networking.internal.knative.dev/serverlessservice=basic-1
 networking.internal.knative.dev/serviceType=Private
 serving.knative.dev/configuration=basic
 serving.knative.dev/configurationGeneration=1
 
serving.knative.dev/configurationUID=4cbbd31b-a712-4e3f-a524-af181bf50662
 serving.knative.dev/revision=basic-1
 
serving.knative.dev/revisionUID=4156d7bc-7743-4ef9-a78c-6f4a57179372
 serving.knative.dev/service=basic
 
serving.knative.dev/serviceUID=8ed0cca8-fe97-44c8-850e-c93e392acd49
   Annotations:  endpoints.kubernetes.io/last-change-trigger-time: 
2024-02-26T13:49:25Z
   Subsets:
 Addresses:  
 NotReadyAddresses:  10.251.159.135
 Ports:
   Name Port  Protocol
      
   http-usermetric  9091  TCP
   http 8012  TCP
   http-queueadm8022  TCP
   http-istio   8012  TCP
   https8112  TCP
   http-autometric  9090  TCP
   
   Events:  
   ```
   The ip address is marked as NotReady. Looking into that...


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1964109957

   Comparing the Knative services before and after the fix in the 3rd scenario, 
I see that when knative trait is enabled, the Knative Service declares the 
following environment variable:
   ```
   - name: CAMEL_KNATIVE_CONFIGURATION
 value: '{"services":[]}'
   ```
   Per the docs, this env var is expected, but I'm not sure whether the service 
list should be empty.


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]



lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1964077004

   @squakez Here is an update with a few other scenarios:
   
   **Scenario 1**
   Quartz integration, Cron Trait configured with fallback:true
   ```
   spec:
 sources:
 - name: flow1.groovy
   content: |-
 from('quartz://flow1/trigger?cron=0+*+*+?+*+*')
.to("https://httpbin.org/delay/2?bridgeEndpoint=true";)
.to("log:info")
 traits:
   cron:
 fallback: true
   ```
   **Results**
   * Camel K created a deployment and not a CronJob (as expected)
   * No Service or Knative Service/Revision was created (as expected)
   * The deployment pod failed with the reported error
   * Disabling the knative trait fixed the error
   
   **Scenario 2**
   Rest Integration, knatice-service trait disabled so the service is internal 
to the cluster only
   ```
   spec:
 sources:
 - name: flow1.groovy
   content: |-
 from('rest:GET:/demo')
.to("https://httpbin.org/delay/2?bridgeEndpoint=true";)
.to("log:info")
 traits:
   knative-service:
 enabled: false
   ```
   **Results**
   * Camel K created a deployment and a ClusterIP Service (as expected)
   * No Knative Service/Revision was created (as expected)
   * The deployment pod failed with the reported error
   * Disabling the knative trait fixed the error
   
   **Scenario 3**
   Rest Integration, knatice-service trait enabled so the service is exposed 
with Knative
   ```
   spec:
 sources:
 - name: flow1.groovy
   content: |-
 from('rest:GET:/demo')
.to("https://httpbin.org/delay/2?bridgeEndpoint=true";)
.to("log:info")
 traits:
   knative-service:
 enabled: true
 minScale: 1
   ```
   **Results**
   * Camel K created a Knative Service (as expected)
   * Knative created 2 services: `basic-1` and `basic-1-private`
   * The deployment pod failed with the reported error
   * Knative revision status remained with Ready = Unknown and Reason = 
Deploying
   * Disabling the knative trait fixed the error, and it changed the number of 
services Knative created: now there are `basic`, `basic-0001` and 
`basic-1-private` services.
   
   
   So now I'm wondering if the Knative trait should play a role in scenarios 
where a service is not created - scenarios 1 & 2. And trying to understand why 
knative didn't create the 3 services in the 3rd scenario.


-- 
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-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [I] Error configuring property: camel.component.test[00001]port[80]tcp.addr because cannot find component with name test[00001]port[80]tcp. [camel-k]