Helm deployment: The Access Key Id you provided does not exist

[gajus]

Getting this error when trying to add source:

Using Helm chart with the following values:

postgresql:
  enabled: true
logs:
  s3:
    enabled: false

[gajus]

Reverting to the commit before this change makes it work.

There is a regression.

[alafanechere]

Hi @gajus your problem happens for a specific source selection or is it common to all sources during set up and you think its related to S3 logs setup. Could you please share your server log?

[alafanechere]

@vnourdin and @davinchia do you have an insight about the root cause of this regression that appeared after merging #8736?

[vnourdin]

I can't find what could trigger such error 🤔
I just renamed the helm value used to set AWS credentials env variables but kept the same default value.
There is also this change, but I don't see why it would create any problem neither.

@gajus, could you compare AWS credentials in the ConfigMap airbyte-env and in the worker env variables both before and after my changes ? If you don't overwrite them, it should always be minio:minio123

[mohamagdy]

@gajus did you upgrade from previous versions of Airbyte and had MinIO running as a dependency or is it a fresh installation of Airbyte?

[gajus]

I did fresh install in both cases. The latest version does not work. The one from a commit from before the one I referenced works fine. I can replicate this consistently since I built and rebuilt our test environment many times.

[mohamagdy]

I see. I had some other issues with the referenced merge listed here.

For me this works:

logs:
  accessKey:
    password: <access-key>
  secretKey:
    password: <secret-key>
  minio:
    enabled: true

# Yes again!
minio:
  accessKey:
    password: <access-key>
  secretKey:
    password: <secret-key>

[thodquach]

I met this problem with default values.yaml.
chart version: "0.39.10-alpha"
How can we fix this for now?

[yoavtzelnick]

Having the same problem as @thodquach .
I think this is caused by 0.39.9-alpha (#13432) with updating the Chart.yaml minio version from 7 to 11.

[stasrelevanceai]

We also faced with this error yesterday. This helped:

minio:
  accessKey:
    password: minio
  secretKey:
    password: minio123
  auth:
   rootUser: minio
   rootPassword: minio123

auth block was added as the latest version minio requires different configuration: https://github.com/bitnami/charts/tree/master/bitnami/minio#to-900

airbyte helm chart should be updated with a newer configuration for minio helm chart.

[OmarSultan85]

@stasrelevanceai Thank for providing that, this worked for me

[isabelbicalho]

Any updates? I get this error with S3 destination

[stasrelevanceai]

@isabelbicalho have you tried this code?
#8805 (comment)

It worked for us. With the new version of minio, braking changes were introduced in helm configuration that needs to be addressed in airbyte helm as well.

[marcosmarxm]

Closing due inactivity. @gajus please test last version of Helm deployment.