Amol Shirke
08/30/2022, 7:01 PMJosh
08/30/2022, 7:28 PMJohn
08/30/2022, 9:11 PMSophia Alice
08/30/2022, 9:16 PMFlow Run Succeeded
but the process doesn’t exit after success and instead hangs. Any idea what’s happening?Matt Melgard
08/30/2022, 9:18 PMJeffrey Lai
08/30/2022, 11:07 PMAdam Brusselback
08/31/2022, 12:41 AMChris L.
08/31/2022, 4:56 AMLow Kim Hoe
08/31/2022, 5:17 AM$ prefect cloud login --key xxx_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
But i get the following error Unable to authenticate with Prefect Cloud. Please ensure your credentials are correct.
My env is pipenv. And I am using prefect 2.2.0
$ prefect --version
2.2.0
And I have created the API Key hereLow Kim Hoe
08/31/2022, 5:20 AMyuvipanda
08/31/2022, 6:29 AMyuvipanda
08/31/2022, 6:29 AMyuvipanda
08/31/2022, 6:31 AMAbimbola Adebayo
08/31/2022, 6:46 AMiñigo
08/31/2022, 7:40 AMOlivér Atanaszov
08/31/2022, 8:29 AMSatsuki Nagae
08/31/2022, 8:56 AMRikimaru Yamaguchi
08/31/2022, 9:43 AMChris L.
08/31/2022, 9:59 AMChris Keeley
08/31/2022, 10:28 AMOluremi Akinwale
08/31/2022, 10:48 AMRahul Kadam
08/31/2022, 11:18 AMFailed to start task for flow run ad860ca0-61df-4055-b3f6-7f48c2d9ead4. Failures: [{'arn': 'arn:aws:ecs:us-east-1:XXXXXXXXXXXX:container-instance/XXXXXXXXXXXX', 'reason': 'RESOURCE:CPU'}, {'arn': 'arn:aws:ecs:us-east-1:XXXXXXXXXXXX:container-instance/XXXXXXXXXXXX', 'reason': 'RESOURCE:MEMORY'}, {'arn': 'arn:aws:ecs:us-east-1:XXXXXXXXXXXX:container-instance/XXXXXXXXXXXX', 'reason': 'RESOURCE:MEMORY'}]
Understandably, its because enough resources are not available on ECS nodes to schedule the tasks when launch type is EC2.
But as per my understanding, in such cases the ECS task should get scheduled with "Provisioning" state, and ECS cluster should scale out and add more instances after which the task would run. However in our case we see above error and the task just fails to schedule.
Is there a specific parameter we are missing which will provide the ECS feature that i mentioned above ? or this is the expected pattern ?Timo
08/31/2022, 11:31 AMprefect deployment build myflow.py:myflow \
--path /prefect/flows/myflow \
-ib docker-container/dev-image \
--name local_docker \
--skip-upload \
--apply
After running the deployment it breaks with "no basic auth credentials".
Inspecting the "Docker Container" block shows that it should use the defined registry block. Double checked the credentials multiple times and successfully logged in with docker login...
I tried the same on 2.2.0 with the same error after executing the deployment :-(Jeff Hale
08/31/2022, 11:36 AMAdam Brusselback
08/31/2022, 12:29 PMMohammad Tami
08/31/2022, 2:23 PMJosh Paulin
08/31/2022, 2:32 PMPrakash Rai
08/31/2022, 2:57 PMJason
08/31/2022, 3:21 PMKhuyen Tran
08/31/2022, 3:31 PM