Cloud Storage Configs are null for GCS logs storage type

  • Is this your first time deploying Airbyte?: No
  • Memory / Disk: not important
  • Deployment: Are you using Docker or Kubernetes deployment? Kubernetes GKE Autopilot
  • Airbyte Version: What version are you using now? from 0.40.26 to 0.40.30
  • The issue is happening during testing the connection of new source
  • Description:

We have airbyte deployed on GKE autopilot, we had the version 0.40.26 and it was working fine without problems. However, after passing to version 0.40.30 and 0.40.32, they have the same problem. We were running into problems when we test the connection of a source. it gives us this error: Internal Server Error: Cannot invoke "" because the return value of "io.airbyte.config.helpers.LogConfigs.getStorageConfigs()" is null
We have the logging part configured to be on GCS bucket, with the variables mounted to the worker:


and also we made sure that we have these variables too with these values:
(we tested both uppercase and lowercase for the ‘GCS’ value)

Like I said, it was working fine with 0.40.26, the logging didn’t have any problem, but it seems like something has changed in later versions.
I have SSH’d to the pods of Workers/Servers to make sure that the variables are mounted with the right values, and everything is OK.

You can find attached the logs that appear in the server when it fails after testing the connection, and another file with the .env file that contains all the variables we mount to the worker.
error-logs.txt (12.9 KB)
variables.txt (3.1 KB)

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.
The Community Assistance Team

Version 0.40.32 is buggy check release notes:
I didn’t find any particular change touching the WORKER_LOGS_STORAGE_TYPE part of the code since v0.40.30. The value you’re using it is correct, the value is uppercase.
Are you able to rollback to 0.40.26? My suggestion is to wait until next release and try again.

I managed to fix it by adding the variables listed above to the server pod !
btw rolling back to .26 wasn’t a good idea, we had some inconsistencies in airbyte’s pg db

thanks !