-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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.
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
PostgreSQL service binding does not get recognised by Quarkus app #30682
Comments
* Disabling the service binding tests caused by quarkusio/quarkus#30682
I'm having a look into this issue |
@mjurc the traces you shared seem to be caused because the Service Binding Operator is not installed. If you install it, then you will reach to the actual issue:
And this issue is caused by the changes in #29702 because the crunchy operator does not provide the I will address this issue by:
|
👍🏼 Let's also add proper warning messages in cases we encounter unexpected values |
Plus, log a warning when the uri property does not have the expected format Fix quarkusio#30682
Plus, log a warning when the uri property does not have the expected format Fix quarkusio#30682
Plus, log a warning when the uri property does not have the expected format Fix quarkusio#30682
Plus, log a warning when the uri property does not have the expected format Fix quarkusio#30682
Okay. @Sgitario can you have a look or do you want me to? |
I'm having a look. |
🙏🏼 |
Hey folks, any updates to this issue? I followed the quickstart guide crunchy operator. Quarkus Version 3.3.0 and still mentioned error. |
Describe the bug
Since Quarkus 2.15, Quarkus application is unable to bind to PostgreSQL service provided by CrunchyDB.
PostgresCluster used:
application.properties
:These settings have worked since Quarkus 2.2.
Expected behavior
Service is bound to Quarkus application and the application launches
Actual behavior
Quarkus fails the service binding, application misses datasource configuration and thus fails to start with
How to Reproduce?
Reproducer is available at https://github.com/quarkus-qe/quarkus-test-suite
cd service-binding/postrgres-crunchy-classic
PostgresCluster
, deploy the application and run crud operations on it:mvn clean verify -Dopenshift
To run with Quarkus that worked with this SB, you can run
mvn clean verify -Dopenshift -Dquarkus.platform.version=2.14.3.Final
To manually deploy the
PostgresCluster
and the application, run the following:Output of
uname -a
orver
Linux tigris 6.1.7-200.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jan 18 17:11:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Output of
java -version
openjdk version "17.0.5" 2022-10-18
GraalVM version (if different from Java)
No response
Quarkus version or git rev
since 2.15.0
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.8.5 (Red Hat 3.8.5-3)
Additional information
This also fails for reactive Hibernate - for the reproducer, see https://github.com/quarkus-qe/quarkus-test-suite/tree/main/service-binding/postgresql-crunchy-reactive.
The application manages to boot there, but it fails when it tries to access the datasource with bogus URL:
The text was updated successfully, but these errors were encountered: