-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
0.2.9
-
False
-
-
False
-
-
Description of the problem:
If workflows are deployed in a separate namespace from the Data Index, they never move to fully running. Logs report a connectivity issue:
2024-04-01 12:00:48,667 WARN [io.agr.pool] (agroal-11) Datasource '<default>': The connection attempt failed. 2024-04-01 12:00:48,675 INFO [io.sma.health] (executor-thread-1) SRHCK01001: Reporting health down status: {"status":"DOWN","checks":[{"name":"SmallRye Reactive Messaging - readiness check","status":"UP"},{"name":"Database connections health check","status":"DOWN","data":{"<default>":"Unable to execute the validation check for the default DataSource: The connection attempt failed."}}]} 2024-04-01 12:00:58,309 WARN [io.agr.pool] (agroal-11) Datasource '<default>': The connection attempt failed. 2024-04-01 12:00:58,311 INFO [io.sma.health] (executor-thread-1) SRHCK01001: Reporting health down status: {"status":"DOWN","checks":[{"name":"SmallRye Reactive Messaging - readiness check","status":"UP"},{"name":"Database connections health check","status":"DOWN","data":{"<default>":"Unable to execute the validation check for the default DataSource: The connection attempt failed."}}]} 2024-04-01 12:01:08,312 WARN [io.agr.pool] (agroal-11) Datasource '<default>': The connection attempt failed.
oc get pods NAME READY STATUS RESTARTS AGE mtaanalysis-7c55bd7b47-2zjmb 0/1 Running 0 29m
If workflows are deployed in the same namespace as the data index and job service, they deploy normally.
How reproducible: 100%
Steps to reproduce:
1. Deploy Orchestrator using chart 0.2.9 and use the following workflow charts:
orchestrator-workflows/greeting 0.4.2 1.16.0 A Helm chart for the greeting serverless workflow orchestrator-workflows/move2kube 0.2.16 1.16.0 A Helm chart to deploy the move2kube workflow. orchestrator-workflows/mta 0.2.16 1.16.0 A Helm chart for MTA serverless workflow orchestrator-workflows/workflows 0.2.24 1.16.0 A Helm chart for serverless workflows
2. Create workflow namespace, copy postgres secret into workflow namespace
3. Deploy workflow in custom namespace and observe the pods
Actual results:
Workflow never deploys, pods never move to be fully Running.
Expected results:
Workflow should deploy normally
- links to