Running the launcher replication-orchestrator failed

Bob_Seehra · February 2, 2023, 8:43pm

Is this your first time deploying Airbyte?: No
OS Version / Instance: Docker/Kubernetes
Memory / Disk: NA
Deployment: Kubernetes
Airbyte Version: 0.40.29
Source name/version: All
Destination name/version: All
Step: The issue is happening during sync
Description: Remove this with the description of your problem.

We upgraded from 0.40.4 to 0.40.29 and have started to experience an error with all syncs/connectors.

Disabling the replication-orchestrator allows the syncs to work, although we still see the same exception in the logs.

CONTAINER_ORCHESTRATOR_ENABLED=false

java.lang.RuntimeException: io.airbyte.workers.exception.WorkerException: Running the launcher replication-orchestrator failed
	at io.airbyte.commons.temporal.TemporalUtils.withBackgroundHeartbeat(TemporalUtils.java:314) ~[io.airbyte-airbyte-commons-temporal-0.40.29.jar:?]
	at io.airbyte.workers.sync.LauncherWorker.run(LauncherWorker.java:116) ~[io.airbyte-airbyte-commons-worker-0.40.29.jar:?]
	at io.airbyte.workers.temporal.TemporalAttemptExecution.lambda$getWorkerThread$5(TemporalAttemptExecution.java:195) ~[io.airbyte-airbyte-workers-0.40.29.jar:?]
	at java.lang.Thread.run(Thread.java:1589) ~[?:?]
Caused by: io.airbyte.workers.exception.WorkerException: Running the launcher replication-orchestrator failed
	at io.airbyte.workers.sync.LauncherWorker.lambda$run$3(LauncherWorker.java:234) ~[io.airbyte-airbyte-commons-worker-0.40.29.jar:?]
	at io.airbyte.commons.temporal.TemporalUtils.withBackgroundHeartbeat(TemporalUtils.java:309) ~[io.airbyte-airbyte-commons-temporal-0.40.29.jar:?]
	... 3 more
Caused by: io.airbyte.workers.exception.WorkerException: Failed to create pod orchestrator-repl-job-81006-attempt-0, pre-existing pod exists which didn't advance out of the NOT_STARTED state.
	at io.airbyte.workers.sync.LauncherWorker.lambda$run$3(LauncherWorker.java:198) ~[io.airbyte-airbyte-commons-worker-0.40.29.jar:?]
	at io.airbyte.commons.temporal.TemporalUtils.withBackgroundHeartbeat(TemporalUtils.java:309) ~[io.airbyte-airbyte-commons-temporal-0.40.29.jar:?]
	... 3 more
Caused by: io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://10.70.128.1/api/v1/namespaces/airbyte-dev/pods. Message: Pod "orchestrator-repl-job-81006-attempt-0" is invalid: [spec.volumes[1].secret.secretName: Required value, spec.containers[0].volumeMounts[1].name: Not found: "airbyte-secret", spec.containers[0].volumeMounts[1].mountPath: Required value, spec.initContainers[0].volumeMounts[1].name: Not found: "airbyte-secret", spec.initContainers[0].volumeMounts[1].mountPath: Required value]. Received status: Status(apiVersion=v1, code=422, details=StatusDetails(causes=[StatusCause(field=spec.volumes[1].secret.secretName, message=Required value, reason=FieldValueRequired, additionalProperties={}), StatusCause(field=spec.containers[0].volumeMounts[1].name, message=Not found: "airbyte-secret", reason=FieldValueNotFound, additionalProperties={}), StatusCause(field=spec.containers[0].volumeMounts[1].mountPath, message=Required value, reason=FieldValueRequired, additionalProperties={}), StatusCause(field=spec.initContainers[0].volumeMounts[1].name, message=Not found: "airbyte-secret", reason=FieldValueNotFound, additionalProperties={}), StatusCause(field=spec.initContainers[0].volumeMounts[1].mountPath, message=Required value, reason=FieldValueRequired, additionalProperties={})], group=null, kind=Pod, name=orchestrator-repl-job-81006-attempt-0, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=Pod "orchestrator-repl-job-81006-attempt-0" is invalid: [spec.volumes[1].secret.secretName: Required value, spec.containers[0].volumeMounts[1].name: Not found: "airbyte-secret", spec.containers[0].volumeMounts[1].mountPath: Required value, spec.initContainers[0].volumeMounts[1].name: Not found: "airbyte-secret", spec.initContainers[0].volumeMounts[1].mountPath: Required value], metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=Invalid, status=Failure, additionalProperties={}).
	at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:682) ~[kubernetes-client-5.12.2.jar:?]
	at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:661) ~[kubernetes-client-5.12.2.jar:?]
	at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:612) ~[kubernetes-client-5.12.2.jar:?]
	at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:555) ~[kubernetes-client-5.12.2.jar:?]
	at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:518) ~[kubernetes-client-5.12.2.jar:?]
	at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleCreate(OperationSupport.java:305) ~[kubernetes-client-5.12.2.jar:?]
	at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleCreate(BaseOperation.java:644) ~[kubernetes-client-5.12.2.jar:?]
	at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleCreate(BaseOperation.java:83) ~[kubernetes-client-5.12.2.jar:?]
	at io.fabric8.kubernetes.client.dsl.base.CreateOnlyResourceOperation.create(CreateOnlyResourceOperation.java:61) ~[kubernetes-client-5.12.2.jar:?]
	at io.fabric8.kubernetes.client.utils.CreateOrReplaceHelper.createOrReplace(CreateOrReplaceHelper.java:48) ~[kubernetes-client-5.12.2.jar:?]
	at io.fabric8.kubernetes.client.dsl.base.BaseOperation.createOrReplace(BaseOperation.java:318) ~[kubernetes-client-5.12.2.jar:?]
	at io.fabric8.kubernetes.client.dsl.base.BaseOperation.createOrReplace(BaseOperation.java:83) ~[kubernetes-client-5.12.2.jar:?]
	at io.fabric8.kubernetes.client.dsl.base.BaseOperation.createOrReplace(BaseOperation.java:308) ~[kubernetes-client-5.12.2.jar:?]
	at io.fabric8.kubernetes.client.dsl.base.BaseOperation.createOrReplace(BaseOperation.java:83) ~[kubernetes-client-5.12.2.jar:?]
	at io.airbyte.workers.process.AsyncOrchestratorPodProcess.create(AsyncOrchestratorPodProcess.java:438) ~[io.airbyte-airbyte-commons-worker-0.40.29.jar:?]
	at io.airbyte.workers.sync.LauncherWorker.lambda$run$3(LauncherWorker.java:190) ~[io.airbyte-airbyte-commons-worker-0.40.29.jar:?]
	at io.airbyte.commons.temporal.TemporalUtils.withBackgroundHeartbeat(TemporalUtils.java:309) ~[io.airbyte-airbyte-commons-temporal-0.40.29.jar:?]
	... 3 more

marcosmarxm · February 2, 2023, 11:02pm

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

khaledalarja · February 7, 2023, 7:35am

were you able to figure out the issue? i am having the same issue

khaledalarja · February 7, 2023, 11:21am

so far putting CONTAINER_ORCHESTRATOR_ENABLED to false has solved my issue, but this should not be considered as a solution since the problem exists somewhere else
@marcosmarxm please do you have any info about this issue?

Bob_Seehra · February 7, 2023, 12:47pm

We haven’t been able to resolve the issue

mr-mcox · February 10, 2023, 5:14pm

I also ran into this issue and appreciate the suggestion of disabling the container orchestrator.

I’m deploying Airbyte 0.40.32 on GKE and experienced this with the a Postgres <-> BigQuery connector.

FWIW, I did some code diving to trace the origins of the Required value, spec.containers[0].volumeMounts[1].name: Not found: "airbyte-secret" error (which seems especially suspicious) and noticed that airbyte/AsyncOrchestratorPodProcess.java at 2e099acc52aeddc172c5ee66ed98426c69449a4a · airbytehq/airbyte · GitHub is the only place where that volume is referenced. I wonder if it’s not being created because of a missing configuration value, but I’m unable to determine what that value may be.

natalyjazzviolin · February 27, 2023, 3:48pm

Hey @Bob_Seehra, could you upgrade to the latest version? We’ve gone through a significant refactor recently.

Bob_Seehra · March 3, 2023, 2:42pm

We updated to the latest version v0.41.0 and the syncs are now working as expected. Thanks @natalyjazzviolin!

Topic		Replies	Views
Issue with Orchestrator Pod in Airbyte on Kubernetes Platform Questions kubernetes , platform , airbyte , sync-issue , container-orchestrator	0	4	November 28, 2024
Error Running Sync with Launcher Replication Orchestrator Connector Questions connector , error , question , sync , launcher-replication-orchestrator	0	19	August 1, 2024
Error running connector with Oracle DB as source and PostgreSQL as destination in Airbyte version 0.50.33 on Kubernetes Connector Questions kubernetes , connector , error , bug , oracle-db	1	29	May 14, 2024
Airbyte Worker Failing to Run Replication-Orchestrator on EKS Platform Questions kubernetes , bug , failure , eks , airbyte-worker	0	130	June 8, 2024
Sync fails due to "Forbidden: pod updates may not change fields other than `spec.containers[].image`, `spec.initContainers[].image`, `spec.activeDeadlineSeconds` or `spec.tolerations` (only additions to existing tolerations)" Platform, Deploy & Infra Issues connectors , kubernetes , deploy	4	3218	October 20, 2022

Running the launcher replication-orchestrator failed

Related topics