Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Integration test fails to start mongo with Liquibase #42453

Closed
vkn opened this issue Aug 9, 2024 · 2 comments · Fixed by #42472
Closed

Integration test fails to start mongo with Liquibase #42453

vkn opened this issue Aug 9, 2024 · 2 comments · Fixed by #42472
Labels
area/liquibase area/mongodb kind/bug Something isn't working
Milestone
3.13.3

Comments

@vkn
Copy link
Contributor

vkn commented Aug 9, 2024

Describe the bug

Mongodb dev services don't start if quarkus.liquibase-mongodb.migrate-at-start=true when running @QuarkusIntegrationTest

Expected behavior

devservices must start mongo container

Actual behavior

Mongodb is not starting

How to Reproduce?

mongodb-quickstart.tar.gz
Unpack and run ./mvnw -Dquarkus.container-image.build=true verify

Output of uname -a or ver

No response

Output of java -version

openjdk version "21.0.3" 2024-04-16 LTS

Quarkus version or git rev

3.13.1

Build tool (ie. output of mvnw --version or gradlew --version)

Apache Maven 3.9.8

Additional information

No response
@vkn vkn added the kind/bug Something isn't working label Aug 9, 2024
@quarkus-bot
Copy link

quarkus-bot bot commented Aug 9, 2024

/cc @andrejpetras (liquibase), @geoand (liquibase), @gsmet (liquibase), @loicmathieu (mongodb)

@gsmet gsmet mentioned this issue Aug 11, 2024
Merged
@gsmet
Copy link
Member

gsmet commented Aug 11, 2024

Actually, the container is started but the MongoDB client cannot connect to the container because it's using the wrong port.

I created a fix here: #42472 .

@gsmet gsmet closed this as completed in e853d39 Aug 12, 2024
@quarkus-bot quarkus-bot bot added this to the 3.14 - main milestone Aug 12, 2024
frne pushed a commit to frne/quarkus that referenced this issue Aug 13, 2024
@gsmet @frne-trifork
Fix connection port for MongoDB dev services using shared network
4ca8ec6 
The hostname was fixed in quarkusio#42065 but when using a shared network and a
container build, the application will connect directly to the container
port so we shouldn't use the exposed port but the original one.

Fixes quarkusio#42453
@gsmet gsmet modified the milestones: 3.14.0.CR1, 3.13.3 Aug 19, 2024
gsmet added a commit to gsmet/quarkus that referenced this issue Aug 19, 2024
@gsmet
Fix connection port for MongoDB dev services using shared network
e0f8bba 
The hostname was fixed in quarkusio#42065 but when using a shared network and a
container build, the application will connect directly to the container
port so we shouldn't use the exposed port but the original one.

Fixes quarkusio#42453

(cherry picked from commit e853d39)
danielsoro pushed a commit to danielsoro/quarkus that referenced this issue Sep 20, 2024
@gsmet @danielsoro
Fix connection port for MongoDB dev services using shared network
df0688e 
The hostname was fixed in quarkusio#42065 but when using a shared network and a
container build, the application will connect directly to the container
port so we shouldn't use the exposed port but the original one.

Fixes quarkusio#42453
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/liquibase area/mongodb kind/bug Something isn't working
Projects
None yet
Milestone
3.13.3
Development

Successfully merging a pull request may close this issue.

Fix connection port for MongoDB dev services using shared network gsmet/quarkus
2 participants
@gsmet @vkn