Problem with Camel Kafka Infra 4.18.0

[christophd]

The Camel Infra service for Kafka in version 4.18.0 causes the Citrus integration test to fail. So I had to keep using 4.17.0 for this infra service.

See the Smart Log Analyzer example: https://github.com/apache/camel-jbang-examples/blob/main/smart-log-analyzer/first-iteration/test/first-iteration.citrus.it.yaml#L1

If you change this to 4.18.0 for camel infra kafka the Camel integration starts failing.

[christophd]

@Croway maybe you can have a look, too. Many thanks!

[Croway]

Thanks for the ping @christophd , the potential issue is related to changes to https://github.com/apache/camel/blob/aed48e70e583267eff1c147216a521ed7c00f1b1/test-infra/camel-test-infra-common/src/main/java/org/apache/camel/test/infra/common/services/ContainerEnvironmentUtil.java#L99 in particular, in camel test infra 4.17, citrus was using the default fixed port (9092 for kafka), and it was working as expected since

variables:
  - name: kafka.broker
    value: localhost:9092

is defined.

In Camel 4.18, a random port is used but the test code still expect kafka to run on 9092. What should be the correct behaviour from citrus perspective? Using random port, or the fixed one?

In case of the fixed one, somehow the property camel.infra.fixedPort=true should be passed to the test infra.
Otherwise, in case the random port approach is correct, the test itself should be updated and the variable ${CITRUS_CAMEL_INFRA_KAFKA_BROKERS} should be used