No data flow controller found when trying an asset transfer

[ftgy]

Hi, I'm trying to transfer an asset between two connectors following the readme.txt using the local deployment.
The contract negotiation i successful, but when I transfer the asset I get this error on the provider-qna side.
Could it be that the data-plane is misconfigured? I'm not modifying anything in the MVD, and just following the guide in the readme.

SEVERE 2024-07-24T14:03:41.629077846 TransferProcess: ID b2b33e40-fad7-4ae7-9411-13e4baf84009. Fatal error while Initiate data flow. Error details: Unable to process transfer b2b33e40-fad7-4ae7-9411-13e4baf84009. No data flow controller found WARNING 2024-07-24T14:03:41.629273198 Unable to process transfer b2b33e40-fad7-4ae7-9411-13e4baf84009. No data flow controller found DEBUG 2024-07-24T14:03:41.629574501 [TransferProcessManagerImpl] TransferProcess b2b33e40-fad7-4ae7-9411-13e4baf84009 is now in state TERMINATING DEBUG 2024-07-24T14:03:41.630575761 TransferProcess: ID b2b33e40-fad7-4ae7-9411-13e4baf84009. Terminate data flow SEVERE 2024-07-24T14:03:41.630843795 TransferProcess: ID b2b33e40-fad7-4ae7-9411-13e4baf84009. Fatal error while Terminate data flow. Error details: Unable to process transfer b2b33e40-fad7-4ae7-9411-13e4baf84009. No data flow controller found WARNING 2024-07-24T14:03:41.630896766 Unable to process transfer b2b33e40-fad7-4ae7-9411-13e4baf84009. No data flow controller found

[paullatzelsperger]

there is an E2E Test that goes through and verifies an entire data transfer using the K8S deployment, so the configuration is definitely working.
without disclosing how you are running this (intellij, k8s), on which OS etc. I won't be able to help. also note, that Windows is not supported at this time as it causes problems with paths all the time.

[ftgy]

I'm running it using intellij, deploying locally with the .run/dataspace.run.xml file, and I'm on Ubuntu 22.04. How hard would it be to modify the k8s test to test a local deployment?

[paullatzelsperger]

How hard would it be to modify the k8s test to test a local deployment?

For you to play around locally, this should be pretty straight forward. Take a look at TransferEndToEndTest.java, you'll likely need to update the URLs and the Provider-ID, i.e. the constants at the top. And don't forget to run the seed.sh.

For a continuous CI/CD situation, we'll stick to K8S though.

[ftgy]

I'll try it, thanks!