Open sivankumar86 opened 6 months ago
@sivankumar86 can you update your issue providing what steps are you running. What version? What cloud provider and Kuberentes version. Share the values you're using. This can help understand what is causing the issue.
@marcosmarxm Thank you for taking a look. It is helm chat and running on Azure aks
Helm chart verions : 0.63.0 k8s 1.26.0
Root causes: I was setting up new sync and destination is "snowflake". It was failing due to snowflake check pod due to permission however, airbyte pod error was misleading with NPE error.
Solution: Provided permission to snowflake airbyte user and issue seems resolved.
It is low priority for now however, it should emit actual error instead of NPE error.
At Airbyte, we seek to be clear about the project priorities and roadmap. This issue has not had any activity for 180 days, suggesting that it's not as critical as others. It's possible it has already been fixed. It is being marked as stale and will be closed in 20 days if there is no activity. To keep it open, please comment to let us know why it is important to you and if it is still reproducible on recent versions of Airbyte.
Topic
K8s Sync NPE exception and it is transient issue. Retry gets success and I am not sure what is actual issue. is it pod creation timeout ?
Relevant information
k8s : Airbyte version 0.55.2
Error:
2024-04-03 20:11:01 platform > 2024-04-03 20:11:01 platform > ----- END CHECK ----- 2024-04-03 20:11:01 platform >
I think it comes from here