Tim Helfensdörfer
09/05/2022, 3:40 PMwork_queue_name
and tags
. Both work queues are running at the moment, e.g. with prefect agent start --work-queue "Production"
. But only the Staging work queue picks up jobs. The production work queue does not.
It is correctly assigned in the cloud ui, i.e. I can see the late jobs in the work queue tab, but the queue does not get any data: (moved to thread)Anna Geller
09/05/2022, 6:16 PMprefect deployment build ... -q Staging
for more info, check this comprehensive guide https://discourse.prefect.io/t/prefect-deployments-faq/1467Tim Helfensdörfer
09/06/2022, 7:50 AMWARNING: Active profile 'production' set by environment variable not found. The default profile will be used instead.
WARNING: Active profile 'production' set by environment variable not found. The default profile will be used instead.
Starting agent with ephemeral API...
___ ___ ___ ___ ___ ___ _____ _ ___ ___ _ _ _____
| _ \ _ \ __| __| __/ __|_ _| /_\ / __| __| \| |_ _|
| _/ / _|| _|| _| (__ | | / _ \ (_ | _|| .` | | |
|_| |_|_\___|_| |___\___| |_| /_/ \_\___|___|_|\_| |_|
Agent started! Looking for work from queue(s): Production...
14:59:17.616 | INFO | prefect.agent - Created work queue 'Production'.
###
### A complete description of a Prefect Deployment for flow 'Calculations: Degree Type Order'
###
name: ****-production
description: null
version: ****
# The work queue that will handle this deployment's runs
work_queue_name: Production
tags:
- production
parameters: {}
schedule: null
infra_overrides: {}
infrastructure:
type: process
env: {}
labels: {}
name: null
command:
- python3
- -m
- prefect.engine
stream_output: true
###
### DO NOT EDIT BELOW THIS LINE
###
flow_name: '****'
manifest_path: null
storage: null
path: /app
entrypoint: ****
parameter_openapi_schema:
title: Parameters
type: object
properties: {}
required: null
definitions: null
Anna Geller
09/06/2022, 8:28 AMTim Helfensdörfer
09/06/2022, 8:30 AMAnna Geller
09/06/2022, 8:34 AMTim Helfensdörfer
09/06/2022, 11:37 AMThis is why the manifest file exists - to detect changes that could break a deployment.
PREFECT_API_URL
in our production docker container. Thats why we got the message from above Starting agent with ephemeral API...
instead of the message we got in our staging container Starting v2.3.1 agent connected to <https://api.prefect.cloud/api/accounts/****/work>
.
Thanks anyways.Anna Geller
09/06/2022, 2:12 PMTim Helfensdörfer
09/06/2022, 2:12 PMAnna Geller
09/06/2022, 2:15 PMTim Helfensdörfer
09/06/2022, 2:24 PMAnna Geller
09/06/2022, 2:26 PMpip install prefect
prefect orion start
Tim Helfensdörfer
09/06/2022, 2:36 PMStarting v2.3.1 agent connected to local sqlite database /path/to/sqlite
• Flag to confirm that you want to connect to the cloud or the local sqlite database prefect agent start --work-queue 'Queue' --cloud
and throw an error if it could not connect to the cloud
In the end, for us, it does not matter anymore what you do about this small issue. But we keep finding these small annoyances and just try to make prefect a better product because, and I want to be honest here, if there would be another product with the same functionality we would have switched by now.Anna Geller
09/06/2022, 2:47 PMTim Helfensdörfer
09/06/2022, 3:10 PM