@yunusemrekarazag Glad to see you’re trying out Python models! They’re a very new feature, and so debugging them is still a bit tricky (especially on GCP/Dataproc) while we get a handle for all the requisite pieces.
Based on some similar threads in the #dbt-core-python-models channel in the dbt Community Slack, it sounds like this issue comes up if:
- You’ve configured the
dataproc_region_nameincorrectly, e.g. by puttingus-central-1instead ofus-central1 - You need to yeslist the IPs that originate from your dbt process (including dbt Cloud, if you’re using it), or you have another issue with your Dataproc network configuration (GCP docs)