Eduardo Ferreira
12/01/2025, 8:56 PMERROR i.a.a.c.c.ClientConfigurationSupport(generateDefaultRetryPolicy$lambda$3):63 - Failed to call unknown. Last response: null
java.io.IOException: HTTP error: 500 Internal Server Error
at io.airbyte.api.client.interceptor.ThrowOn5xxInterceptor.intercept(ThrowOn5xxInterceptor.kt:16)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
at okhttp3.internal.connection.RealCall.execute(RealCall.kt:154)
at dev.failsafe.okhttp.FailsafeCall.lambda$execute$0(FailsafeCall.java:117)
at dev.failsafe.Functions.lambda$get$0(Functions.java:46)
at dev.failsafe.internal.RetryPolicyExecutor.lambda$apply$0(RetryPolicyExecutor.java:74)
at dev.failsafe.SyncExecutionImpl.executeSync(SyncExecutionImpl.java:187)
at dev.failsafe.CallImpl.execute(CallImpl.java:33)
at dev.failsafe.okhttp.FailsafeCall.execute(FailsafeCall.java:121)
at io.airbyte.api.client.generated.WorkloadOutputApi.writeWorkloadOutputWithHttpInfo(WorkloadOutputApi.kt:376)
at io.airbyte.api.client.generated.WorkloadOutputApi.writeWorkloadOutput(WorkloadOutputApi.kt:62)
at io.airbyte.workers.workload.WorkloadOutputWriter.writeOutputThroughServer(WorkloadOutputWriter.kt:82)
at io.airbyte.workers.workload.WorkloadOutputWriter.write(WorkloadOutputWriter.kt:65)
at io.airbyte.connectorSidecar.ConnectorWatcher.handleException(ConnectorWatcher.kt:207)
at io.airbyte.connectorSidecar.ConnectorWatcher.run(ConnectorWatcher.kt:83)
at io.airbyte.connectorSidecar.ApplicationKt.main(Application.kt:22)
at io.airbyte.connectorSidecar.ApplicationKt.main(Application.kt)kapa.ai
12/01/2025, 8:56 PMThrowOn5xxInterceptor, which is expected behavior when the server returns a 5xx.[[Error 500 issue](https://github.com/airbytehq/airbyte/issues/53609); [abctl 500 issue](https://github.com/airbytehq/airbyte/issues/58587)] From the provided sources, there isn’t a specific root cause or fix documented for this exact writeWorkloadOutput 500 on Helm v2. Similar reports around Helm v2 / workload API show generic connectivity / 5xx problems, and the guidance there is essentially to: 1. Check server / controller logs around the same time The real error is usually logged on the server or workload‑API side; the 500 is just what the sidecar sees. None of the referenced GitHub or forum threads include a resolved “root cause” for this kind of 500.[[Helm error 68136](https://github.com/airbytehq/airbyte/issues/68136); [Helm chart 2.0.0 issues](https://github.com/airbytehq/airbyte/issues/68134)] 2. Verify the Helm deployment & versions In similar Kubernetes/Helm threads, support generally recommends upgrading to the latest chart / app version when seeing unexplained runtime 5xx errors, because some of them have been fixed in newer releases.[[K8s forum 0.40.x](https://discuss.airbyte.io/t/2861); [Helm chart 2.0.0 issues](https://github.com/airbytehq/airbyte/issues/68134)] 3. Confirm internal service connectivity Other Helm v2 issues show ConnectException / failure to reach *-workload-api-server-svc or *-server-svc in‑cluster.[[Helm error 68136](https://github.com/airbytehq/airbyte/issues/68136); [Helm chart 2.0.0 issues](https://github.com/airbytehq/airbyte/issues/68134)] For your case, ensure: - The workload API server pod is running and healthy. - Its service DNS name and port are correct for the chart version you’re using. - NetworkPolicies or service mesh are not blocking traffic from sidecar pods to the workload API service. 4. Look for known API mismatches / schema issues In at least one 500‑error case, the cause was a mismatch between API schema and backend fields (missing fields like `codename`/`definitionId`).[[Error 500 issue](https://github.com/airbytehq/airbyte/issues/53609)] The knowledge sources don’t show an equivalent confirmed schema bug for writeWorkloadOutput, but if you see schema/JSON errors in the server logs when the 500 happens, that would be a similar pattern. Because the shared sources don’t include a resolution for WorkloadOutputApi.writeWorkloadOutput returning 500 on Helm v2, I can’t point to a concrete fix beyond these checks. The next step is: - Capture the Airbyte server and workload‑API logs around the same timestamp as this stack trace and inspect/log any 5xx stack traces there. - If you don’t find a clear cause, open or update a GitHub issue with: - Exact Airbyte image versions and Helm chart version (v2.x.y), - Those server/workload‑API logs, - This sidecar stack trace. The maintainers have been using that information to diagnose similar Helm‑related 5xx issues.[[Helm error 68136](https://github.com/airbytehq/airbyte/issues/68136); [Helm chart 2.0.0 issues](https://github.com/airbytehq/airbyte/issues/68134)]