-
Bug
-
Resolution: Done
-
Normal
-
None
-
None
-
False
-
-
False
-
-
Description of the problem: The openshift-mta operator is not deployed as part of the MTA workflow Helm chart, which causes errors in deployment.
How reproducible: 100%
Steps to reproduce:
1. Deploy Orchestrator using Helm chart 0.1.21
2. Deploy MTA workflow using Helm chart 0.2.5
3. Run workflow
Expected results: Expect operator to be deployed and workflow to run normally
Actual results: Errors such as the following:
2024-02-13 09:51:45,903 ERROR [org.jbp.wor.ins.imp.WorkflowProcessInstanceImpl] (executor-thread-4) Unexpected error while executing node getApplication in process instance e406fa1f-9d3c-4927-bd4a-9f05b856fd1f: org.jbpm.workflow.instance.WorkflowRuntimeException: [MTAAnalysis:e406fa1f-9d3c-4927-bd4a-9f05b856fd1f - getApplication:6] -- RESTEASY004655: Unable to invoke request: java.net.UnknownHostException: mta-ui.openshift-mta.svc.cluster.local: Name or service not known
