You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "pai911 (via GitHub)" <gi...@apache.org> on 2023/12/20 11:18:29 UTC
[I] Jitpack not working as expected [camel-k]
pai911 opened a new issue, #4998:
URL: https://github.com/apache/camel-k/issues/4998
### What happened?
When running the example code of Jitpack (https://github.com/apache/camel-k-examples/tree/main/generic-examples/jitpack)
```
kamel run Jitpack.java -d github:squakez/samplejp:1.0.0-SNAPSHOT
```
It seemed the integration always goes into Error status without clear error message.
```
╰─ kamel get
NAME PHASE KIT
jitpack Error camel/kit-cm1cpb4qqlkcmha0bpv0
```
I looked up the status of several components.
### Steps to reproduce
_No response_
### Relevant log output
_No response_
### Camel K version
_No response_
--
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
Re: [I] Jitpack not working as expected [camel-k]
Posted by "pai911 (via GitHub)" <gi...@apache.org>.
pai911 commented on issue #4998:
URL: https://github.com/apache/camel-k/issues/4998#issuecomment-1866020471
Thank you for the clue!
It seems my setting.xml uses company Nexus server as proxy.
To make it work, I had to add the following to Maven `settings.xml`
(in addition to other basic configs, like adding Jitpack repositories)
```
<mirrors>
<mirror>
<id>repo-through-public</id>
<mirrorOf>*,!jitpack.io</mirrorOf>
<url>https://COMPANY-MAVEN-REPO/</url>
</mirror>
<mirror>
<id>jitpack.io</id>
<mirrorOf>jitpack.io</mirrorOf>
<url>https://jitpack.io</url>
</mirror>
</mirrors>
```
It'll make Jitpack related dependencies go around company Nexus.
However, we can also do it the proper way -- that is make company Nexus server support Jitpack
See: https://github.com/jitpack/jitpack.io/issues/506#issuecomment-267338823
Thank you @squakez
I think we can close this issue?
--
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
Re: [I] Jitpack not working as expected [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #4998:
URL: https://github.com/apache/camel-k/issues/4998#issuecomment-1864345126
Strange. It works for me:
```
$ kamel run Jitpack.java -d github:squakez/samplejp:1.0.0-SNAPSHOT --dev
Integration "jitpack" created
Progress: integration "jitpack" in phase Initialization
...
[1] 2023-12-20 11:50:41,554 INFO [org.apa.cam.k.Runtime] (main) Apache Camel K Runtime 3.2.0
[1] 2023-12-20 11:50:41,556 INFO [org.apa.cam.qua.cor.CamelBootstrapRecorder] (main) Bootstrap runtime: org.apache.camel.quarkus.main.CamelMainRuntime
[1] 2023-12-20 11:50:41,559 INFO [org.apa.cam.mai.MainSupport] (main) Apache Camel (Main) 4.0.0 is starting
[1] 2023-12-20 11:50:41,588 INFO [org.apa.cam.k.sup.SourcesSupport] (main) Loading routes from: SourceDefinition{name='Jitpack', language='java', type='source', location='file:/etc/camel/sources/Jitpack.java', }
[1] 2023-12-20 11:50:42,484 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Apache Camel 4.0.0 (camel-1) is starting
[1] 2023-12-20 11:50:42,494 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Routes startup (started:1)
[1] 2023-12-20 11:50:42,494 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Started route1 (timer://tick)
[1] 2023-12-20 11:50:42,495 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Apache Camel 4.0.0 (camel-1) started in 10ms (build:0ms init:0ms start:10ms)
[1] 2023-12-20 11:50:42,498 INFO [io.quarkus] (main) camel-k-integration 2.1.0 on JVM (powered by Quarkus 3.2.6.Final) started in 2.244s.
[1] 2023-12-20 11:50:42,499 INFO [io.quarkus] (main) Profile prod activated.
[1] 2023-12-20 11:50:42,499 INFO [io.quarkus] (main) Installed features: [camel-bean, camel-core, camel-java-joor-dsl, camel-k-core, camel-k-runtime, camel-kubernetes, camel-log, camel-timer, cdi, kubernetes-client, smallrye-context-propagation, vertx]
[1] 2023-12-20 11:50:43,520 INFO [info] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: v1.0.0-SNAPSHOT:HELLO]
```
Maybe your failure is related to the registry or any other cause. Have a look at the [Camel Integration troubleshooting guide](https://camel.apache.org/camel-k/2.1.x/troubleshooting/troubleshooting.html).
--
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
Re: [I] Jitpack not working as expected [camel-k]
Posted by "pai911 (via GitHub)" <gi...@apache.org>.
pai911 commented on issue #4998:
URL: https://github.com/apache/camel-k/issues/4998#issuecomment-1864880495
Is there a way to see any more detailed error message than the following?
```
status:
conditions:
- lastTransitionTime: "2023-12-20T11:31:13Z"
lastUpdateTime: "2023-12-20T11:33:36Z"
message: 'integration kit camel/kit-cm1d10cqqlkcmha0bq30 is in state "Error".
Failure: failure while building project: : exit status 1'
reason: IntegrationKitAvailable
status: "False"
type: IntegrationKitAvailable
dependencies:
- camel:log
- camel:timer
- github:squakez/samplejp:main
- mvn:org.apache.camel.k:camel-k-runtime
- mvn:org.apache.camel.quarkus:camel-quarkus-java-joor-dsl
digest: vx7jL06sJVJ9Nd9ZGCk0Upvp7teRikbc1dIHO6QLu0uA
integrationKit:
name: kit-cm1d10cqqlkcmha0bq30
namespace: camel
lastInitTimestamp: "2023-12-20T11:31:13Z"
observedGeneration: 3
phase: Error
profile: Kubernetes
runtimeProvider: quarkus
runtimeVersion: 3.2.0
version: 2.1.0
```
It only happens when I try to run the Jitpack example. Is it possible that the registry issue only affects Jitpack example?
### With Jitpack
```
╰─ kamel run Jitpack.java -d github:squakez/samplejp:1.0.0-SNAPSHOT --dev
Integration "jitpack" created
Progress: integration "jitpack" in phase Initialization
Integration "jitpack" in phase "Initialization"
Progress: integration "jitpack" in phase Building Kit
Condition "IntegrationPlatformAvailable" is "True" for Integration jitpack: camel/camel-k
Integration "jitpack" in phase "Initialization"
Integration "jitpack" in phase "Building Kit"
Condition "IntegrationKitAvailable" is "False" for Integration jitpack: integration kit camel/kit-cm1ib0kqqlkcmha0bq6g is in state "Build Running"
Build "kit-cm1ib0kqqlkcmha0bq6g", created by Integration "jitpack", changed phase to "Initialization" (recovery 2 of 5)
Build "kit-cm1ib0kqqlkcmha0bq6g", created by Integration "jitpack", changed phase to "Scheduling" (recovery 2 of 5)
Build "kit-cm1ib0kqqlkcmha0bq6g", created by Integration "jitpack", changed phase to "Pending" (recovery 2 of 5)
Build "kit-cm1ib0kqqlkcmha0bq6g", created by Integration "jitpack", changed phase to "Running" (recovery 2 of 5)
Build "kit-cm1ib0kqqlkcmha0bq6g", created by Integration "jitpack", changed phase to "Failed" (recovery 2 of 5)
Build "kit-cm1ib0kqqlkcmha0bq6g", created by Integration "jitpack", changed phase to "Initialization" (recovery 3 of 5)
Build "kit-cm1ib0kqqlkcmha0bq6g", created by Integration "jitpack", changed phase to "Scheduling" (recovery 3 of 5)
Build "kit-cm1ib0kqqlkcmha0bq6g", created by Integration "jitpack", changed phase to "Pending" (recovery 3 of 5)
Build "kit-cm1ib0kqqlkcmha0bq6g", created by Integration "jitpack", changed phase to "Running" (recovery 3 of 5)
(combined from similar events): Build "kit-cm1ib0kqqlkcmha0bq6g", created by Integration "jitpack", changed phase to "Failed" (recovery 3 of 5)
```
### Without Jitpack
```
╰─ kamel run Sample.java --dev
Integration "sample" created
Progress: integration "sample" in phase Initialization
Progress: integration "sample" in phase Building Kit
Progress: integration "sample" in phase Deploying
Progress: integration "sample" in phase Running
Condition "IntegrationPlatformAvailable" is "True" for Integration sample: camel/camel-k
Integration "sample" in phase "Initialization"
Integration "sample" in phase "Building Kit"
Condition "IntegrationKitAvailable" is "True" for Integration sample: kit-clspaa75nhnt34k4ek30
Integration "sample" in phase "Deploying"
Condition "CronJobAvailable" is "False" for Integration sample: different controller strategy used (deployment)
Condition "DeploymentAvailable" is "True" for Integration sample: deployment name is sample
Condition "ServiceAvailable" is "False" for Integration sample: no http service required
Condition "ExposureAvailable" is "False" for Integration sample: no service defined
Condition "Ready" is "False" for Integration sample
Integration "sample" in phase "Running"
Condition "Ready" is "True" for Integration sample: 1/1 ready replicas
...
[1] 2023-12-20 17:38:33,667 INFO [org.apa.cam.k.Runtime] (main) Apache Camel K Runtime 3.2.0
[1] 2023-12-20 17:38:33,672 INFO [org.apa.cam.qua.cor.CamelBootstrapRecorder] (main) Bootstrap runtime: org.apache.camel.quarkus.main.CamelMainRuntime
[1] 2023-12-20 17:38:33,676 INFO [org.apa.cam.mai.MainSupport] (main) Apache Camel (Main) 4.0.0 is starting
[1] 2023-12-20 17:38:33,735 INFO [org.apa.cam.k.sup.SourcesSupport] (main) Loading routes from: SourceDefinition{name='Sample', language='java', type='source', location='file:/etc/camel/sources/Sample.java', }
[1] 2023-12-20 17:38:35,260 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Apache Camel 4.0.0 (camel-1) is starting
[1] 2023-12-20 17:38:35,275 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Routes startup (started:1)
[1] 2023-12-20 17:38:35,275 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Started route1 (timer://tick)
[1] 2023-12-20 17:38:35,276 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Apache Camel 4.0.0 (camel-1) started in 14ms (build:0ms init:0ms start:14ms)
```
Any other info is much appreciated!
--
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
Re: [I] Jitpack not working as expected [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #4998:
URL: https://github.com/apache/camel-k/issues/4998#issuecomment-1865850504
The guide I've provided above [1] should give you more details on how to troubleshoot an Integration. In your case what is clearly happening is a Maven build failure. I guess there could be some problem accessing the Jitpack repository by your cluster. You can have a more detailed trace checking the log of the Camel K operator Pod (`kubectl logs camel-k-operator-xyz`).
[1] https://camel.apache.org/camel-k/2.1.x/troubleshooting/troubleshooting.html
--
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
Re: [I] Jitpack not working as expected [camel-k]
Posted by "pai911 (via GitHub)" <gi...@apache.org>.
pai911 closed issue #4998: Jitpack not working as expected
URL: https://github.com/apache/camel-k/issues/4998
--
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