Replication pod creation fails (KubeClientException) but UI/Public API still reports sync as successful
- Linguagem predominante
- Python
- Estrelas
- 22.1k
- Forks
- 5.4k
- Merge médio
- 5h
- PRs com merge (30d)
- 671
Descrição
### Helm Chart Version
2.0.1
### What step the error happened?
During the Sync
### Relevant information
### Key Issues
1. Sync fails during replication pod launch:
`io.airbyte.workers.exception.KubeClientException: Failed to create pod replication-job-185-attempt-0`
2. Despite the pod creation failure, both the Airbyte UI and the public API still report the sync as **successful** (`connectionSyncStatus: "synced"`), causing a status inconsistency.
### Relevant log output
```shell
2025-12-23 14:01:02 Platform ERROR Stage Pipeline Exception:
io.airbyte.workload.launcher.pipeline.stages.model.StageError:
io.airbyte.workers.exception.KubeClientException:
Failed to create pod replication-job-185-attempt-0.
2025-12-23 14:01:02 Platform INFO Attempting to update workload:
dc6b4366-d9c8-49d4-86c3-616da54f97a9_185_0_sync to FAILED.
2025-12-23 14:01:02 Platform INFO Pipeline aborted after error for workload:
dc6b4366-d9c8-49d4-86c3-616da54f97a9_185_0_sync.
----- START POST REPLICATION OPERATIONS -----
2025-12-23 14:01:02 Platform INFO No post-replication operation(s) to perform.
----- END POST REPLICATION OPERATIONS -----
```
---
**Internal Tracking:** https://github.com/airbytehq/oncall/issues/11093
Guia de contribuição
Avaliação
Esta issue ainda não foi avaliada.