https://linen.dev logo
Join Slack
Powered by
When I stand-up Airbyte using Helm chart 0.42.4, t...
# replication-troubleshooting
d
When I stand-up Airbyte using Helm chart 0.42.4, the minio pod is stuck in pending and will not start. I have had this problem periodically from version to version and I do not understand the cause. Is there a way around minio?
m
Hello Don, did you change anything in Helm values or using default? Can you share logs from the airbyte-server?
d
It was working with kubernetes version 1.21, but I am using 1.24 and having issues. I am using the following values
Copy code
values: {
        webapp: {
          service: {
            type: 'LoadBalancer',
            protocol: 'TCP',
            port: 80,
            targetPort: 80,
            annotations: {
              '<http://service.beta.kubernetes.io/aws-load-balancer-internal|service.beta.kubernetes.io/aws-load-balancer-internal>': 'true',
            },
          },
        },
        externalDatabase: {
          host: postgresRds.dbInstanceEndpointAddress,
          port: postgresRds.dbInstanceEndpointPort,
          database: 'airbyte',
          user: 'airbyte',
          password: 'password',
        },
        postgresql: {
          enabled: false,
        },
      },
    });
This is from describe minio
Copy code
Events:
  Type     Reason            Age    From               Message
  ----     ------            ----   ----               -------
  Warning  FailedScheduling  13m    default-scheduler  no nodes available to schedule pods
  Warning  FailedScheduling  13m    default-scheduler  0/1 nodes are available: 1 node(s) had untolerated taint {<http://node.kubernetes.io/not-ready|node.kubernetes.io/not-ready>: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
  Warning  FailedScheduling  2m33s  default-scheduler  running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition
Server logs look like this:
Copy code
2022-12-08 19:01:34 INFO i.a.s.RequestLogger(filter):112 - REQ 10.0.0.149 GET 200 /api/v1/health
2022-12-08 19:01:43 INFO i.a.s.RequestLogger(filter):112 - REQ 10.0.0.239 GET 200 /api/v1/health
2022-12-08 19:01:44 INFO i.a.s.RequestLogger(filter):112 - REQ 10.0.0.149 GET 200 /api/v1/health
2022-12-08 19:01:44 INFO i.a.s.RequestLogger(filter):112 - REQ 10.0.0.149 GET 200 /api/v1/health
Cannot start publish with com.van.logging.aws.S3PublishHelper@7d786ef8 due to error: Cannot start publishing: Unable to execute HTTP request: Connect to airbyte-minio-svc:9000 [airbyte-minio-svc/172.20.201.58] failed: Connection refused
here is the pvc output:
Copy code
NAME                                     STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   AGE
airbyte-minio-pv-claim-airbyte-minio-0   Pending                                      gp2            17m
Copy code
VolumeMode:    Filesystem
Used By:       airbyte-minio-0
Events:
  Type    Reason                Age                   From                         Message
  ----    ------                ----                  ----                         -------
  Normal  WaitForFirstConsumer  17m                   persistentvolume-controller  waiting for first consumer to be created before binding
  Normal  WaitForPodScheduled   16m (x3 over 17m)     persistentvolume-controller  waiting for pod airbyte-minio-0 to be scheduled
  Normal  ExternalProvisioning  2m17s (x60 over 16m)  persistentvolume-controller  waiting for a volume to be created, either by external provisioner "<http://ebs.csi.aws.com|ebs.csi.aws.com>" or manually created by system administrator
@Marcos Marx (Airbyte) thanks for taking a look. Please let me know if you need more information.
m
@Don H I think this is the issue: https://github.com/airbytehq/airbyte/issues/15523
d
Thanks. If it doesn't work on 1.24 yet, what is the latest version that should work?
m
Not sure, but probably 1.21
2 Views
Open in Slack
PreviousNext
Powered by