When invoke flow, I got request failed to be processed.

[tim64195419]

I don't know how to fixing this problem?

I got deploy/function logs look like

[sherry10]

I got the same error, and I have no idea. Could you please help us? @s8sg

[s8sg]

It seems the name of flow function flowName its getting as 10

[sherry10]

@s8sg Sorry, I have found the problem. Link to https://github.com/faasflow/runtime/issues/1

[s8sg]

@sherry10 Did you found the solution ?

[tim64195419]

@sherry10 Can you share how to fixing this problem?

[sherry10]

@s8sg @tim64195419 I have changed several workflow names and have found that the url OpenFaasExecutor built always get the flow name '10'. And I have found the runtime pkg provides a method getWorkflowNameFromHost to get workflow name, but the host is not what the runtime expect. So I changed the config directFunctions of OpenFaas gateway, which will invoke functions passing through the faas-netes provider instead of directly over overlay network by DNS name. Then the flow name is correct and the function works.

[tim64195419]

@sherry10 I follow your step then solved function name is 10 problem, but another problem is when set directfunction=true, faasflow pipeline can't pass the value with s3(minio) . Have you got this problem?

[dimgiagos44]

@tim64195419 Did you solve the latter problem with directFunctions=true? It also happens to me when i try to invoke both replica pods of a function but with directFunctions=true, just one is invoked always as if load balancing not works from the gateway..

[dimgiagos44]

Hack solution here: faasflow/runtime#1 (comment)