-
Bug
-
Resolution: Unresolved
-
Undefined
-
1.2.0-rc9
-
False
-
-
False
-
-
-
Important
Description of the problem:
Running the MTV plan workflow with migrationName field value consisting of upper case values fails the workflow, but both the UI and the default logging does not show any indication of what caused the error.
The only way to identify the reason for the error is to enable quarkus debug logging and run again, which shows that it is a validation issue:
2024-08-20 20:00:41,502 DEBUG [org.apa.htt.headers] (executor-thread-3) http-outgoing-0 << Content-Length: 962 2024-08-20 20:00:41,505 DEBUG [org.apa.htt.imp.exe.MainClientExec] (executor-thread-3) Connection can be kept alive indefinitely 2024-08-20 20:00:41,513 DEBUG [org.apa.htt.wire] (executor-thread-3) http-outgoing-0 << "art and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')","field":"metadata.name"}]},"code":422}[\n]" 2024-08-20 20:00:41,514 DEBUG [org.apa.htt.imp.con.PoolingHttpClientConnectionManager] (executor-thread-3) Connection [id: 0][route: {s}->https://api.ocp-edge-orchestrator-0.qe.lab.redhat.com:6443] can be kept alive indefinitely 2024-08-20 20:00:41,514 DEBUG [org.apa.htt.imp.con.DefaultManagedHttpClientConnection] (executor-thread-3) http-outgoing-0: set socket timeout to 0 2024-08-20 20:00:41,514 DEBUG [org.apa.htt.imp.con.PoolingHttpClientConnectionManager] (executor-thread-3) Connection released: [id: 0][route: {s}->https://api.ocp-edge-orchestrator-0.qe.lab.redhat.com:6443][total available: 1; route allocated: 1 of 50; total allocated: 1 of 50] 2024-08-20 20:00:41,520 ERROR [org.jbp.wor.ins.imp.NodeInstanceImpl] (executor-thread-3) capture error: org.jbpm.workflow.instance.WorkflowRuntimeException: [mtv-plan:4cead2ff-3b78-413a-b108-fcc7f22c2a15 - createPlan:[uuid=7]] -- Unknown error, status code 422 at org.jbpm.workflow.instance.node.WorkItemNodeInstance.getExceptionScopeInstance(WorkItemNodeInstance.java:211) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.handleException(WorkItemNodeInstance.java:205) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.processWorkItemHandler(WorkItemNodeInstance.java:195) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:169)
How reproducible:
100%
Steps to reproduce:
1. Run mtv plan workflow
2. For the migrationName choose something with capital letters, such as testMigration
3. Excute the workflow
Actual results:
workflow errors out for unknown reason
Expected results:
workflow errors out and explains why it failed
- links to
