davsclaus commented on issue #2868:
URL:
https://github.com/apache/camel-kamelets/issues/2868#issuecomment-4766187982
> :robot: _Claude Code on behalf of Claus Ibsen_
## Analysis
The 22 test failures have **two distinct root causes**:
### 1. KafkaIT (3 failures) — Orphaned variable in `application.properties`
`kafka.securityProtocol=${kafka.securityProtocol}` is referenced in
`tests/camel-kamelets-itest/src/test/resources/kafka/application.properties`
but **never defined** in any Kafka test YAML file. This variable is vestigial —
commit bd3322920 renamed the Kafka properties (`kafka.user`/`kafka.password` →
`kafka.saslUsername`/`kafka.saslPassword`) but left the `securityProtocol`
line. The Kafka pipe definitions don't use it either (they use `saslAuthType:
'PLAIN'`).
**Fix:** Removed the orphaned line — committed to `main`.
### 2. CommonIT (12 failures) + likely others — CAMEL-23594: URL-encoded
Kamelet properties
The full stack trace reveals:
```
InvalidMediaTypeException: Invalid mime type "application%2Fjson": does not
contain '/'
```
Camel's YAML DSL URL-encodes Kamelet endpoint property values, turning
`application/json` into `application%2Fjson`. This affects all tests that use
Kamelets with properties containing `/` or other URL-sensitive characters
(http-source, http-sink, transformation, crypto, filter, header kamelets).
This is a **Camel core** bug — tracked as
[CAMEL-23594](https://issues.apache.org/jira/browse/CAMEL-23594) with fix PR
[apache/camel#23391](https://github.com/apache/camel/pull/23391). The CommonIT
failures will be resolved once that fix is merged and the kamelets project
picks up the fixed Camel version.
### 3. AwsIT, JiraIT, SlackIT — May be related or separate
These may also be affected by CAMEL-23594 if their Kamelet properties hit
the URL-encoding issue, or they may have separate testcontainers/timing issues
that need independent investigation.
--
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]
