[
https://issues.apache.org/jira/browse/CAMEL-26326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Netherton reassigned CAMEL-26326:
---------------------------------------
Assignee: James Netherton
> camel-iggy: camel-iggy-test-infra container exits on startup
> ------------------------------------------------------------
>
> Key: CAMEL-26326
> URL: https://issues.apache.org/jira/browse/CAMEL-26326
> Project: Camel
> Issue Type: Test
> Reporter: James Netherton
> Assignee: James Netherton
> Priority: Minor
>
> The Iggy 0.9.0 container exits on startup, so the camel-iggy integration
> tests fail.
> Since the test image was upgraded to apache/iggy:0.9.0 (57a3047978c3), the
> Iggy container exits during startup and every camel-iggy integration test
> fails with a ContainerLaunchException. The tests are disabled on CI
> (@DisabledIfSystemProperty(named = "ci.env.name")), so this was not noticed.
> IggyContainer sets IGGY_TCP_ADDRESS=0.0.0.0:8090. Iggy 0.9.0 rejects a
> wildcard TCP address:
> {noformat}
> CONFIG - tcp.address binds the wildcard 0.0.0.0:8090, which says which
> interfaces this node accepts on rather than where a client reaches it, so
> cluster metadata would carry no address for this node.
> Error: Config(InvalidConfigurationValue)
> {noformat}
> The 0.9.0 default (127.0.0.1:8090) is not reachable through the mapped port,
> so dropping the variable is not enough. Going back to the 0.8.0 image does
> not work either: the camel-iggy client is 0.9.0 and times out against a 0.8.0
> server.
> Possible fix: bind the TCP listener to an address that is both concrete and
> reachable from the host, for example the container's own network address, or
> use whatever Iggy 0.9.0 provides for this.
> Reproduce:
> {noformat}
> mvn verify -pl components/camel-iggy
> {noformat}
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
