lsergio commented on issue #5706:
URL: https://github.com/apache/camel-k/issues/5706#issuecomment-2248694107
A new scenario. Now when a quartz integration is created:
```
apiVersion: camel.apache.org/v1
kind: Integration
metadata:
name: deploy-a41357e7-14c0-4a64-9933-80044f023ad3-381
spec:
sources:
- name: main.yaml
content: |-
- from:
uri: quartz://ipaas/trigger?cron=0+*+*+?+*+*
steps:
- log:
message: "It worked"
traits:
camel:
runtimeVersion: 3.8.1
cron:
fallback: true
```
I see the conditions:
```
- firstTruthyTime: "2024-07-24T18:42:31Z"
lastTransitionTime: "2024-07-24T18:42:31Z"
lastUpdateTime: "2024-07-24T18:42:31Z"
message: deployment name is
deploy-a41357e7-14c0-4a64-9933-80044f023ad3-323
reason: DeploymentAvailable
status: "True"
type: DeploymentAvailable <-- DeploymentAvailable and not
DeploymentDeploymentAvailable (when status is True)
- lastTransitionTime: "2024-07-24T18:42:31Z"
lastUpdateTime: "2024-07-24T18:42:31Z"
message: different controller strategy used (deployment)
reason: KnativeServiceNotAvailable
status: "False"
type: KnativeServiceKnativeServiceAvailable <-- KnativeService prefix
duplicated
- lastTransitionTime: "2024-07-24T18:42:31Z"
lastUpdateTime: "2024-07-24T18:42:31Z"
message: fallback strategy selected
reason: CronJobNotAvailableReason
status: "False"
type: CronCronJobAvailable <-- Cron prefix duplicated
```
It seems like the relased Trait name is being prefixed to the type value
when the status is False.
--
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
