https://linen.dev logo
Join Slack
Powered by
My jobs do not start. Attempt 1 runs forever. ```...
# replication-ask-ai
j
My jobs do not start. Attempt 1 runs forever.
Copy code
abctl local status


  INFO    Using Kubernetes provider:
            Provider: kind
            Kubeconfig: /root/.airbyte/abctl/abctl.kubeconfig
            Context: kind-airbyte-abctl
 SUCCESS  Found Docker installation: version 26.1.4                                                                                                                                 
 SUCCESS  Existing cluster 'airbyte-abctl' found                                                                                                                                    
  INFO    Found helm chart 'airbyte-abctl'                                                                                                                                          
            Status: deployed
            Chart Version: 2.0.19
            App Version: 2.0.1
  INFO    Found helm chart 'ingress-nginx'                                                                                                                                          
            Status: deployed
            Chart Version: 4.15.1
            App Version: 1.15.1
  INFO    Airbyte should be accessible via <http://localhost:8000>                                                                                                                    
  INFO    A new release of abctl is available: v0.30.3 -> v0.30.4                                                                                                                   
          Updating to the latest version is highly recommended
k
This looks like a known issue affecting users who upgraded to Airbyte v2. Your status shows Chart Version: 2.0.19 / App Version: 2.0.1, which matches the reported problem. Root Cause After upgrading to Airbyte v2, the 
dataplane_group_id
in the workspace table may be mismatched or null, preventing jobs from launching. [jobs not starting] Fix You need to update the 
dataplane_group_id
on the workspace table in the database. The steps reported by users who resolved this: 1. Check the available dataplane groups:SELECT * FROM public.dataplane_group; 2. Update the workspace to use the correct (enabled) dataplane group:UPDATE public.workspace SET dataplane_group_id = 'enabled_dataplane_group_id';Use the 
id
of the enabled dataplane group from step 1. [jobs not starting] Alternatively, if you are configuring via Helm values, adding the following before upgrading prevents the issue:
Copy code
global:
  dataplaneGroups:
    defaultDataplaneGroupName: "AUTO"
The 
"default"
value is also reported to work for Airbyte 2.x installations. [jobs not starting] Also noted: Your status output shows a new version of 
abctl
is available (
v0.30.3 → v0.30.4
). It's recommended to update it, though this is separate from the jobs issue. You can upgrade with:
Copy code
curl -LsfS https://get.airbyte.com | bash -
[upgrading abctl] 👍 0 button 👎 0 button ℹī¸ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
j
@kapa.ai I am not using an external database
k
Since you're using the internal (bundled) Postgres database with 
abctl
, here's how to apply the dataplane group fix directly: 1. Export the kubeconfig so 
kubectl
can connect to your cluster:export KUBECONFIG="$HOME/.airbyte/abctl/abctl.kubeconfig" 2. Connect to the database pod:kubectl exec -it -n airbyte-abctl airbyte-db-0 -- /bin/bash psql -U airbyte db-airbyte 3. Check the dataplane groups:SELECT id, name FROM dataplane_group;You may see two rows — one named 
AUTO
and one unnamed. The workload-launcher is likely registered under the unnamed group, while workloads are routed to the 
AUTO
group. [dataplane mismatch] 4. Move all dataplanes to the 
AUTO
group:UPDATE dataplane SET dataplane_group_id = ( SELECT id FROM dataplane_group WHERE name = 'AUTO' LIMIT 1 ) WHERE dataplane_group_id != ( SELECT id FROM dataplane_group WHERE name = 'AUTO' LIMIT 1 );[dataplane mismatch] 5. Exit psql and the pod:\q exit 6. Restart the workload-launcher:kubectl rollout restart deployment/airbyte-abctl-workload-launcher -n airbyte-abctl After the restart, check the workload-launcher logs for lines like:
Copy code
INFO  Resuming ApiQueuePoller with <AUTO-group-id> and high
INFO  Resuming ApiQueuePoller with <AUTO-group-id> and default
This confirms the launcher is now polling the correct group and jobs should start. [dataplane mismatch] > ⚠ī¸ Note: This fix may need to be reapplied after every 
abctl local install
run, as the bootloader recreates the mismatch on each startup. [dataplane mismatch] 👍 0 button 👎 0 button ℹī¸ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
j
@kapa.ai How do I check the workload-launcher logs
k
You can check the workload-launcher logs using `kubectl`:
Copy code
kubectl logs -l app.kubernetes.io/name=workload-launcher --namespace airbyte-abctl --tail=100
Since you're using 
abctl
, make sure your kubeconfig is set first:
Copy code
export KUBECONFIG="$HOME/.airbyte/abctl/abctl.kubeconfig"
After restarting the workload-launcher, look for these lines to confirm it's polling correctly: [dataplane mismatch]
Copy code
INFO  Resuming ApiQueuePoller with <group-id> and high
INFO  Resuming ApiQueuePoller with <group-id> and default
If you only see 
PodSweeper
cycle messages and no 
ApiQueuePoller
lines, the dataplane group mismatch is still present and the launcher is not picking up any workloads. [dataplane mismatch] 👍 0 button 👎 0 button ℹī¸ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
2 Views
Open in Slack
PreviousNext
Powered by