Error creating source in Airbyte helm chart deployment on Kubernetes

Summary

The user is facing errors when trying to create a source in Airbyte deployed via Helm chart on Kubernetes. The error message indicates an ActivityFailure related to ‘RunWithWorkload’. Additionally, there are errors related to ‘GetTaskQueueUserData’ and ‘IdNotFoundExceptionHandler’. The issue seems intermittent.


Question

I’ve deployed helm chart version 1.1.0 on kuberetes, but am running into an error when trying to create a source:

	at java.base/java.lang.Thread.getStackTrace(Thread.java:2450)
	at io.temporal.internal.sync.ActivityStubBase.execute(ActivityStubBase.java:49)
	at io.temporal.internal.sync.ActivityInvocationHandler.lambda$getActivityFunc$0(ActivityInvocationHandler.java:83)
	at io.temporal.internal.sync.ActivityInvocationHandlerBase.invoke(ActivityInvocationHandlerBase.java:60)
	at jdk.proxy2/jdk.proxy2.$Proxy90.runWithWorkload(Unknown Source)
	at io.airbyte.workers.temporal.check.connection.CheckConnectionWorkflowImpl.run(CheckConnectionWorkflowImpl.java:46)
	at CheckConnectionWorkflowImplProxy.run$accessor$KGUoxZck(Unknown Source)
	at CheckConnectionWorkflowImplProxy$auxiliary$Oort8IuM.call(Unknown Source)
	at io.airbyte.micronaut.temporal.TemporalActivityStubInterceptor.execute(TemporalActivityStubInterceptor.java:79)
	at CheckConnectionWorkflowImplProxy.run(Unknown Source)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at io.temporal.internal.sync.POJOWorkflowImplementationFactory$POJOWorkflowImplementation$RootWorkflowInboundCallsInterceptor.execute(POJOWorkflowImplementationFactory.java:339)
	at io.temporal.internal.sync.POJOWorkflowImplementationFactory$POJOWorkflowImplementation.execute(POJOWorkflowImplementationFactory.java:314)
	at io.temporal.internal.sync.WorkflowExecutionHandler.runWorkflowMethod(WorkflowExecutionHandler.java:70)
	at io.temporal.internal.sync.SyncWorkflow.lambda$start$0(SyncWorkflow.java:135)
	at io.temporal.internal.sync.CancellationScopeImpl.run(CancellationScopeImpl.java:102)
	at io.temporal.internal.sync.WorkflowThreadImpl$RunnableWrapper.run(WorkflowThreadImpl.java:107)
	at io.temporal.worker.ActiveThreadReportingExecutor.lambda$submit$0(ActiveThreadReportingExecutor.java:53)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)```
however, the check intermittently works.

in temporal i'm seeing a bunch of
```│ {"level":"info","ts":"2024-10-15T23:15:10.721Z","msg":"matching client encountered error","service":"matching","error":"unknown method GetTaskQueueUserData for service temporal.server.api.matchingservice.v1.MatchingService","service-error-type":"serviceerror.Unimplemented","logging │```
Also seeing this error in the server:
```│ 2024-10-15 23:11:06 ERROR i.a.c.s.e.h.IdNotFoundExceptionHandler(handle):33 - Not found exception class NotFoundKnownExceptionInfo {                                                                                                                                                       │
│     id: null                                                                                                                                                                                                                                                                               │
│     message: Id not found: Could not find configuration for STANDARD_SYNC: 3edc1db4-4564-4743-b355-a4c481d25d10.                                                                                                                                                                           │
│     exceptionClassName: io.airbyte.commons.server.errors.IdNotFoundKnownException                                                                                                                                                                                                          │
│     exceptionStack: [io.airbyte.commons.server.errors.IdNotFoundKnownException: Id not found: Could not find configuration for STANDARD_SYNC: 3edc1db4-4564-4743-b355-a4c481d25d10.,     at io.airbyte.commons.server.errors.handlers.IdNotFoundExceptionHandler.handle(IdNotFoundExceptio │
│     rootCauseExceptionClassName: java.lang.Class                                                                                                                                                                                                                                           │
│     rootCauseExceptionStack: [io.airbyte.commons.server.errors.IdNotFoundKnownException: Could not find configuration for STANDARD_SYNC: 3edc1db4-4564-4743-b355-a4c481d25d10.,     at io.airbyte.server.apis.ApiHelper.execute(ApiHelper.java:32),     at io.airbyte.server.apis.Connecti │
│ }```
anyone encountered any of these / have any idea how to deal with them?

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1729034219461979) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["error", "source-creation", "airbyte", "helm-chart", "kubernetes", "temporal", "activityfailure", "gettaskqueueuserdata", "idnotfoundexceptionhandler"]
</sub>