pkalsi97 commented on PR #6408:
URL: https://github.com/apache/camel-k/pull/6408#issuecomment-3649616218
@squakez Here are some more findings
```
=== RUN TestPipeBuildDontRun/build_and_dont_run_pipe
binding "pipe-deploygfnaz" created
=== RUN TestPipeBuildDontRun/deploy_the_pipe
Integration "pipe-deploygfnaz" deployed
...
Integration Status:
conditions:
- message: 'error during trait customization: kamelets trait configuration
failed:
ConfigMap "pipe-deploygfnaz-kamelet-log-sink-template" not found'
reason: InitializationFailed
status: "False"
type: Ready
phase: Error
generatedSources:
- contentRef: pipe-deploygfnaz-kamelet-log-sink-template # ConfigMap
MISSING
from-kamelet: true
name: log-sink.yaml
- contentRef: pipe-deploygfnaz-kamelet-timer-source-template
from-kamelet: true
name: timer-source.yaml
Found 0 deployments
Found 0 pods
--- FAIL: TestPipeBuildDontRun (203.80s)
--- PASS: TestPipeBuildDontRun/build_and_dont_run_pipe (23.58s)
--- FAIL: TestPipeBuildDontRun/deploy_the_pipe (180.07s)
FAIL
```
As per my understanding and looking at the flow and doing some digging my
findings are that this is related to **gc.go** file in trait.
**Explanation:** I think the GC trait assumes `BuildComplete` phase always
means "undeploy cleanup". However, `BuildComplete` after
`--dont-run-after-build` is not an undeploy, it's the initial build state where
resources should be preserved. Hence the `Deploy` step is unable to find
ConfigMap.
Let me know if you resonate with this findinding. We can create an issue and
deal with it in a separate PR.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
