Ferdinand von den Eichen
02/01/2023, 12:32 PMSubmission failed. Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/prefect_aws/ecs.py", line 797, in _create_task_and_wait_for_start task = self._run_task(ecs_client, task_run) File "/usr/local/lib/python3.9/site-packages/prefect_aws/ecs.py", line 1458, in _run_task return ecs_client.run_task(**task_run)["tasks"][0] File "/usr/local/lib/python3.9/site-packages/botocore/client.py", line 508, in _api_call return self._make_api_call(operation_name, kwargs) File "/usr/local/lib/python3.9/site-packages/botocore/client.py", line 915, in _make_api_call raise error_class(parsed_response, operation_name) botocore.errorfactory.ClusterNotFoundException: An error occurred (ClusterNotFoundException) when calling the RunTask operation: Cluster not found. The above exception was the direct cause of the following exception: RuntimeError: Failed to run ECS task, cluster 'prefect' not found. Confirm that the cluster is configured in your region.
Edit Bonus Question: How would you debug this kind of issue? The main AWS exceptions seems to be suppressed unfortunately…Christopher Boyd
02/01/2023, 2:28 PMaws ecs list-clusters
and see the other accounts clusters. If you can’t, then I would expect it to be an AWS / permissions issue firstFerdinand von den Eichen
02/01/2023, 3:49 PMaws ecs list-clusters
and all of the AWS cli is on a per account basis, right? So it will only ever show the clusters from the active profile. Here’s the result from one of the accounts.
{
"clusterArns": [
"arn:aws:ecs:eu-central-1:123456789:cluster/prefect"
]
}
Can you confirm that an agent in cluster A can in principal schedule tasks on a different cluster? I briefly skimmed over the source code and it seemed unlikely, that that was possible…