Issues with Min.IO dev bucket not found during Airbyte sync job

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

Users experiencing sudden issues with Min.IO not finding the dev bucket during Airbyte sync jobs, leading to job failures. Questioning if it’s related to an upgrade issue and if Airbyte sync jobs need to be rebuilt.


Question

Anyone else have “sudden” issues with http://Min.IO|Min.IO not being able to find the dev bucket all of a sudden? As shown from the attached logs, a sync job starts up and attempts to access airbyte-dev-logs bucket but fails. All of my sync jobs are failing due to this issue.

I’m wondering if it’s due to an upgrade issue; perhaps the Airbyte sync jobs need to be rebuilt? Does anyone have any insight into this?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["min.io", "dev-bucket", "sync-job", "airbyte", "upgrade-issue", "job-failure"]
2

This error is shown from the Airbyte UI:
> Internal Server Error: The specified bucket does not exist (Service: S3, Status Code: 404, Request ID: 17D18584FC747683, Extended Request ID: dd9025bab4ad464b049177c95eb6ebf374d3b3fd1af9251148b658df7ac2e3e8)