-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
False
-
-
False
-
-
Description of the problem:
When installing Orchestrator on a cluster existing RHDH the sonataflow-platform Pods report that they can't connect to the database on startup
How reproducible:
Steps to reproduce:
See slack thread: https://redhat-internal.slack.com/archives/C059YMMB664/p1727869819610849
Actual results:{}
Caused by: org.flywaydb.core.internal.exception.FlywaySqlException: Unable to obtain connection from database: Acquisition timeout while waiting for new connection ----------------------------------------------------------------------------------------------- SQL State : null Error Code : 0 Message : Acquisition timeout while waiting for new connection
Expected results:
Data base connection is successful
- is blocked by
-
FLPATH-1754 Parameterize Network Policies when created for an existing RHDH in a different namespace
- ON_QA
- is depended on by
-
FLPATH-1828 Add network policy to allow communication with sonataflow-infra
- In Progress
- links to