citrusframework / citrusframework/yaks
Unable to lookup camel integration status in local mode
- Dominant language
- Java
- Stars
- 90
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
I am trying to run the local test with [camel-k example](https://github.com/citrusframework/yaks/tree/main/examples/camel-k) on my VM.
```
$ yaks run integration.feature --local
```
The test will get stuck on `TEST STEP 3: camel-k:verify-integration` and retry to find the integration status until it times out or max attempt exceeded.
The output log look like this:
```
...
DEBUG| TEST STEP 3: camel-k:verify-integration
INFO | Verify Camel K integration 'hello-world'
INFO | Waiting for integration 'hello-world' to be in state 'Running'
DEBUG| Full Camel JBang command is: -Dcamel.jbang.version=4.1.0 camel@apache/camel ps
DEBUG| Writing file resource: '878951-output.txt' (encoding is 'UTF-8')
INFO | Waiting for integration 'hello-world' to be in state 'Running'- retry in 5000 ms
DEBUG| Full Camel JBang command is: -Dcamel.jbang.version=4.1.0 camel@apache/camel ps
DEBUG| Writing file resource: '879084-output.txt' (encoding is 'UTF-8')
INFO | Waiting for integration 'hello-world' to be in state 'Running'- retry in 5000 ms
...
```
Also, when I run `camel ps` command, it shows the integration is in 'Running' status.
```
$ camel ps
PID NAME READY STATUS AGE
878922 hello-world 1/1 Running 2m13s
879960 timer-to-log 1/1 Running 1m4s
```
### Environment
OS: `Red Hat Enterprise Linux release 8.8 (Ootpa)`
jbang version: `0.116.0`
Camel version: `4.6.0`
YAKS version: `0.19.2`
A full set of the test project and log files are provided for investigation: [yaks-camel-k-local-issue.zip](https://github.com/user-attachments/files/15721897/yaks-camel-k-local-issue.zip)
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce with `yaks run integration.feature --local` from the linked camel-k example and focus on the `camel-k:verify-integration` step. Compare its status lookup output with `camel ps`; done means a locally Running integration is recognized and the test no longer retries until timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100