Jeff Charbeneau
08/01/2023, 4:51 PMNate
08/01/2023, 5:29 PMJeff Charbeneau
08/01/2023, 5:34 PMprefect-2-agent-*
pod, leading me to believe we're using the Prefect k8s agent, and not the k8s worker.
Below are some pod logs from a recent flow run that had the described behavior.
In the Prefect UI, the flow changed from "Crashed" to "Running" around the time that this log message was printed.
19:21:05.042 | INFO | Flow run 'phi652-alterf' - Downloading flow code from storage at None
Thanks in advance for your thoughts.Nate
08/03/2023, 4:06 PMc4_job_manager.c4_error.C4Error: ('Job be7bajuioxg6gvfnhcufc6 failed, detail=, output={}, ', 'For logs, see <https://relativity.splunkcloud.com/en-US/app/search/search?q=search%20index%3Dr1_k8s_logs_prod%20source%3D*be7bajuioxg6gvfnhcufc6*&display.page.search.mode=verbose&dispatch.sample_ratio=1&earliest=-30m%40m&latest=now>')
can you explain what this is? is there some way it would revive a process that prefect has lost touch with (after a Crash of sorts)Jeff Charbeneau
08/03/2023, 4:31 PMNate
08/03/2023, 4:36 PMJeff Charbeneau
08/03/2023, 4:58 PM