Mongodb connection string argument not passed when starting native integration tests

[nicolas-vivot]

Describe the bug

I recently tried to upgrade from Quarkus 2.7.6 to 2.11.1 and found some issues when running integration tests for a native build with maven, using mvn clean verify -Pnative.

The issue is the mongodb driver not being able to connect to the server, timing out when some of the integration test try to access the database.

To be more specific, this is only happening when performing a second group of tests using a different profile.
As you know, tests (native or not) using different profiles are grouped per profile in order to optimize the number of time the application / quarkus is rebooted to execute all tests.

The first set of integration test is working fine, the following command is run to start the application, right after popping the mongodb container:

Executing "/my-service-runner -Dquarkus.http.port=8081 -Dquarkus.http.ssl-port=8444 -Dtest.url=http://localhost:8081 -Dquarkus.log.file.path=/path/to/my/service/target/quarkus.log -Dquarkus.log.file.enable=true -Dquarkus.mongodb.connection-string=mongodb://localhost:49291/databasename"

with the port number being randomized.

But when the application is shutdown and restarted with a new fresh mongodb container, the command ommit the quarkus.mongodb.connection-string argument: (and adding a few ones i have no idea what for)

Executing "my-service-runner -Dquarkus.http.port=8081 -Dquarkus.http.ssl-port=8444 -Dtest.url=http://localhost:8081 -Dquarkus.log.file.path=/path/to/the/service/target/quarkus.log -Dquarkus.log.file.enable=true -Dquarkus.configuration.build-time-mismatch-at-runtime=fail -Dtoken.generator.secret=test -Dquarkus.profile=int-test -Dtoken.generator.issuer=integration-tests -Dtoken.generator.validity-delay=5"

The consequence is the service timing out on the tentative to connect to the mongodb server, as it tries by default to connect on the default mongodb port 127.0.0.1:27017 which surely cannot match the auto randomized port used by the dev services.

Failing since Quarkus 2.10.0 ?

After checking each version upgrade, i could finally spot the culprit version of Quarkus, the 2.10.0 (was still working fine on the 2.9.2, no matter wich jdk / graalvm or mandrel distribution is used)

I found the following ticket fixing something related to connection string / context information for the mongodb-client integrated into the 2.10.0-RC build and thus in the 2.10.0-Final release of Quarkus, could it be somehow related ?

Expected behavior

The native integration tests using multiple profiles should not fail for connectivity reasons.

Actual behavior

Since the mongo connection string is not passed anymore from the second boot / second profile, all tests needing a connection to the mongodb are failling.

How to Reproduce?

You should be able to reproduce it by using this reproducer

Requirements & how to reproduce in the readme.

[quarkus-bot]

/cc @Karm, @evanchooly, @galderz, @loicmathieu, @zakkak

[geoand]

Would you be able to supply a reproducer project?

Thanks

[nicolas-vivot]

@geoand

Added to the How to Reproduce section

[geoand]

Thanks for the reproducer. #27082 takes care of the issue

[nicolas-vivot]

@geoand By the way, will that fix be backported into a 2.11.2 / 2.10.5 ?

[geoand]

That's the plan