Deploy Kubernetes(EKS): Unable to launch airbyte using helm charts

US-Thakur · September 21, 2022, 9:00am

Is this your first time deploying Airbyte?: Yes
OS Version / Instance: Ubuntu 18… are some example remove it with yours
Memory / Disk: you can use something like 16Gb / 1 Tb
Deployment: Kubernetes
Airbyte Version: v0.40.6
Source name/version:
Destination name/version:
Step: The issue is happening while setting up airbyte using helm chart
Description:

Reason for failure : Error: INSTALLATION FAILED: failed pre-install: timed out waiting for the condition

Followed following steps to setup airbyte :

Created namespace airbyte : kubectl create ns airbyte
Build helm dependencies : helm dependency build --debug -n airbyte
Install airbyte : helm install airbyte -n airbyte . --debug
LOGS :

client.go:556: [debug] Add/Modify event for airbyte-airbyte-bootloader: ADDED
client.go:615: [debug] Pod airbyte-airbyte-bootloader pending
client.go:556: [debug] Add/Modify event for airbyte-airbyte-bootloader: MODIFIED
client.go:615: [debug] Pod airbyte-airbyte-bootloader pending
client.go:556: [debug] Add/Modify event for airbyte-airbyte-bootloader: MODIFIED
client.go:615: [debug] Pod airbyte-airbyte-bootloader pending
client.go:556: [debug] Add/Modify event for airbyte-airbyte-bootloader: MODIFIED
client.go:617: [debug] Pod airbyte-airbyte-bootloader running
client.go:556: [debug] Add/Modify event for airbyte-airbyte-bootloader: MODIFIED
client.go:617: [debug] Pod airbyte-airbyte-bootloader running
client.go:556: [debug] Add/Modify event for airbyte-airbyte-bootloader: MODIFIED
client.go:617: [debug] Pod airbyte-airbyte-bootloader running
Error: INSTALLATION FAILED: failed pre-install: timed out waiting for the condition
helm.go:88: [debug] failed pre-install: timed out waiting for the condition
INSTALLATION FAILED
main.newInstallCmd.func2
        helm.sh/helm/v3/cmd/helm/install.go:127
github.com/spf13/cobra.(*Command).execute
        github.com/spf13/cobra@v1.2.1/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
        github.com/spf13/cobra@v1.2.1/command.go:974
github.com/spf13/cobra.(*Command).Execute
        github.com/spf13/cobra@v1.2.1/command.go:902
main.main
        helm.sh/helm/v3/cmd/helm/helm.go:87
runtime.main
        runtime/proc.go:225
runtime.goexit
        runtime/asm_amd64.s:1371

This leads to pod status :

kubectl get pods -n airbyte
NAME                             READY   STATUS     RESTARTS   AGE
airbyte-airbyte-bootloader       1/2     NotReady   0          27m
airbyte-db-5965d9c677-nwnb6      2/2     Running    1          28m
airbyte-minio-797fd9d6cf-5676p   2/2     Running    0          27m

kubectl describe pod -n airbyte airbyte-airbyte-bootloader

Events:
  Type     Reason     Age                From                                    Message
  ----     ------     ----               ----                                    -------
  Normal   Scheduled  32m                default-scheduler                       Successfully assigned airbyte/airbyte-airbyte-bootloader to ip-10-202-15-253.ec2.internal
  Normal   Pulling    32m                kubelet, ip-10-202-15-253.ec2.internal  Pulling image "docker.io/istio/proxyv2:1.7.0"
  Normal   Pulled     32m                kubelet, ip-10-202-15-253.ec2.internal  Successfully pulled image "docker.io/istio/proxyv2:1.7.0" in 109.488976ms
  Normal   Created    32m                kubelet, ip-10-202-15-253.ec2.internal  Created container istio-validation
  Normal   Started    32m                kubelet, ip-10-202-15-253.ec2.internal  Started container istio-validation
  Normal   Pulling    32m                kubelet, ip-10-202-15-253.ec2.internal  Pulling image "airbyte/bootloader:0.40.5"
  Normal   Pulled     32m                kubelet, ip-10-202-15-253.ec2.internal  Successfully pulled image "airbyte/bootloader:0.40.5" in 5.193570738s
  Normal   Created    32m                kubelet, ip-10-202-15-253.ec2.internal  Created container airbyte-bootloader-container
  Normal   Started    32m                kubelet, ip-10-202-15-253.ec2.internal  Started container airbyte-bootloader-container
  Normal   Pulling    32m                kubelet, ip-10-202-15-253.ec2.internal  Pulling image "docker.io/istio/proxyv2:1.7.0"
  Normal   Pulled     32m                kubelet, ip-10-202-15-253.ec2.internal  Successfully pulled image "docker.io/istio/proxyv2:1.7.0" in 112.645118ms
  Normal   Created    32m                kubelet, ip-10-202-15-253.ec2.internal  Created container istio-proxy
  Normal   Started    32m                kubelet, ip-10-202-15-253.ec2.internal  Started container istio-proxy
  Warning  Unhealthy  32m (x2 over 32m)  kubelet, ip-10-202-15-253.ec2.internal  Readiness probe failed: Get "http://192.168.16.120:15021/healthz/ready": dial tcp 192.168.16.120:15021: connect: connection refused

Bootloader container log snippet:

2022-09-21 07:58:26 INFO i.a.b.SecretMigrator(migrateSources):96 - Migrating Sources
2022-09-21 07:58:26 INFO i.a.b.SecretMigrator(migrateDestinations):120 - Migration Destinations
2022-09-21 07:58:26 INFO i.a.b.BootloaderApp(lambda$new$0):132 - Secrets successfully migrated.
2022-09-21 07:58:26 INFO i.a.b.BootloaderApp(lambda$new$0):135 - Loaded seed data..
2022-09-21 07:58:26 INFO i.a.b.BootloaderApp(load):177 - Finished running post load Execution.
2022-09-21 07:58:26 INFO i.a.b.BootloaderApp(load):179 - Finished bootstrapping Airbyte environment.
2022-09-21 07:58:26 INFO c.z.h.HikariDataSource(close):350 - HikariPool-1 - Shutdown initiated...

airbyte-db-container log when its crashed once:

kubectl logs -n airbyte -f airbyte-db-5965d9c677-nwnb6 -c airbyte-db-container --previous

/usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/000_init.sql
ALTER SYSTEM
CREATE DATABASE
You are now connected to database "airbyte" as user "airbyte".
2022-09-21 07:58:11.385 UTC [52] ERROR:  role "docker" does not exist
2022-09-21 07:58:11.385 UTC [52] STATEMENT:  GRANT ALL ON
	DATABASE airbyte TO docker;
psql:/docker-entrypoint-initdb.d/000_init.sql:12: ERROR:  role "docker" does not exist

Could someone advice what could be the issue here?
Thanks in advance.

marcosmarxm · September 21, 2022, 3:03pm

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

marcosmarxm · September 23, 2022, 4:12pm

Team is working to improve the Helm Chart and for next week it will be unstable. Can you try latets version?

m8m · November 4, 2022, 8:01am

Is there any progress with this issue? seems like I’m having the same problem

US-Thakur · November 4, 2022, 8:43am

@m8m Please check if there is a istio or any other side container running along with the bootloader container in the bootloader pod. My issue got resolved when I stopped using istio for airbyte deployment.

m8m · November 7, 2022, 2:13am

I’m trying to install with default values, following in the tutorial, on a new/clean eks cluster (tried both managed and fargate)

Topic		Replies	Views
Deploy Kubernetes: Unable to launch airbyte using helm charts Platform, Deploy & Infra Issues getting-started , kubernetes , deploy	7	1650	July 14, 2022
Deploy EKS - failed pre-install: timed out waiting for the condition Platform, Deploy & Infra Issues getting-started , deploy	3	1210	November 10, 2022
Install airbyte in kubenates with helm chart Platform, Deploy & Infra Issues getting-started , kubernetes , deploy	5	1865	July 14, 2022
Deploy failed with default values using helm to AWS EKS Platform, Deploy & Infra Issues getting-started , deploy	2	763	February 5, 2023
Unable to upgrade to v0.39.4-alpha or later via Helm chart Platform, Deploy & Infra Issues kubernetes , deploy	5	556	July 14, 2022

Deploy Kubernetes(EKS): Unable to launch airbyte using helm charts

Related Topics