You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "gansheer (via GitHub)" <gi...@apache.org> on 2023/10/02 14:46:28 UTC
Re: [I] Error log traces after integration error [camel-k]
gansheer commented on issue #4781:
URL: https://github.com/apache/camel-k/issues/4781#issuecomment-1743158504
From what I gathered this happens when the integration kit did not manage to build correctly and ends up in failure after 5 failed builds:
* integrationkit:
```yaml
status:
conditions:
- lastTransitionTime: "2023-10-02T13:40:05Z"
lastUpdateTime: "2023-10-02T13:40:05Z"
message: IntegrationPlatform (camel-k)
reason: IntegrationPlatformAvailable
status: "True"
type: IntegrationPlatformAvailable
digest: vU8KNPqHgejR-MytUTqoY4dbP4gi3nktmOKfeEGJdYco
failure:
reason: 'failure while building project: : exit status 1'
recovery:
attempt: 5
attemptMax: 5
attemptTime: "2023-10-02T13:43:32Z"
time: "2023-10-02T13:41:17Z"
observedGeneration: 1
phase: Error
platform: camel-k
runtimeProvider: quarkus
runtimeVersion: 3.2.0
version: 2.1.0-SNAPSHOT
```
* integration:
```yaml
status:
conditions:
- firstTruthyTime: "2023-10-02T13:40:05Z"
lastTransitionTime: "2023-10-02T13:40:05Z"
lastUpdateTime: "2023-10-02T13:40:05Z"
message: default/camel-k
reason: IntegrationPlatformAvailable
status: "True"
type: IntegrationPlatformAvailable
- lastTransitionTime: "2023-10-02T13:40:05Z"
lastUpdateTime: "2023-10-02T13:43:35Z"
message: integration kit default/kit-ckdcgdf5tdfig6lsvu30 is in state "Error"
reason: IntegrationKitAvailable
status: "False"
type: IntegrationKitAvailable
dependencies:
- camel:timer
- mvn:jakarta.annotation:jakarta.annotation-api:1.3.5.redhat-00002
- mvn:org.apache.camel.k:camel-k-runtime
- mvn:org.apache.camel.quarkus:camel-quarkus-java-joor-dsl
digest: vjUJOZpjQiNq3c7_97pi0DdC-HixiwRz_wSyy7OIHoCE
integrationKit:
name: kit-ckdcgdf5tdfig6lsvu30
namespace: default
lastInitTimestamp: "2023-10-02T13:40:05Z"
observedGeneration: 1
phase: Error
platform: camel-k
profile: Kubernetes
runtimeProvider: quarkus
runtimeVersion: 3.2.0
version: 2.1.0-SNAPSHOT
```
What I am trying to understand is how the integration's lifecycle should go on in this state:
* should we be able to identify that a kit already exists and is in error before or during this code:
https://github.com/apache/camel-k/blob/46001e85280ef904549053e2eb4fff5070dd0e00/pkg/controller/integration/monitor.go#L115-L119
* Can the integration kit in failure could end up in success ? Or would it always end up as new integration kit ?
--
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