@kapa.ai Just upgraded to version 2.0.1, and all running jobs show "No logs found for this job." What is causing this error?

In 2.x there are a few known upgrade-related issues that can cause jobs to appear stuck with no logs: 1. Duplicate / mismatched dataplane groups after upgrade to 2.0 After upgrading, some installs end up with two rows in

public.dataplane_group

(one from before and one created after the upgrade). Jobs are queued to dataplane A while the workload launcher listens to dataplane B, so no worker pods start and the UI shows no logs. The reported workaround is to update the

dataplane_group_id

in

public.workspace

to point to the correct (active) dataplane group. [[No jobs after v2](https://github.com/airbytehq/airbyte/issues/68196); [dataplane mismatch](https://github.com/airbytehq/airbyte/issues/68115)] 2. Jobs hanging due to MinIO / storage issues (logs backend) In some cases, all syncs hang and log retrieval breaks because the MinIO storage used for logs is full or corrupted. Users have fixed this by deleting and recreating the MinIO persistent volume (which clears existing logs) or by increasing the storage attached to MinIO. [[All sync jobs hanging](https://github.com/airbytehq/airbyte/issues/55812)] Given your symptoms (“No logs found for this job.” after upgrade to 2.0.1), the most likely causes from the available information are: - A dataplane group mismatch in the Airbyte DB; or - A problem with the MinIO / storage volume used for logs. If checking or editing the database is acceptable in your environment, compare

public.dataplane_group

and

public.workspace.dataplane_group_id

as described in the linked issue, and also verify that your MinIO (or equivalent) volume has sufficient free space and is healthy.