Hi when i’m try to update airbyte from

0.39.13

to

0.40.17

via helm chart I encounter the following error on server pod:

2022-11-02 15:28:00 INFO c.z.h.HikariDataSource(<init>):80 - HikariPool-2 - Starting...
2022-11-02 15:28:00 INFO c.z.h.HikariDataSource(<init>):82 - HikariPool-2 - Start completed.
2022-11-02 15:28:00 DEBUG c.z.h.p.HikariPool(logPoolState):414 - HikariPool-1 - Before cleanup stats (total=0, active=0, idle=0, waiting=0)
2022-11-02 15:28:00 DEBUG c.z.h.p.HikariPool(logPoolState):414 - HikariPool-1 - After cleanup  stats (total=0, active=0, idle=0, waiting=0)
2022-11-02 15:28:00 DEBUG c.z.h.p.HikariPool(fillPool):521 - HikariPool-1 - Fill pool skipped, pool has sufficient level or currently being filled (queueDepth=0).
2022-11-02 15:28:00 DEBUG c.z.h.p.HikariPool(logPoolState):414 - HikariPool-2 - Before cleanup stats (total=0, active=0, idle=0, waiting=0)
2022-11-02 15:28:00 DEBUG c.z.h.p.HikariPool(logPoolState):414 - HikariPool-2 - After cleanup  stats (total=0, active=0, idle=0, waiting=0)
2022-11-02 15:28:00 DEBUG c.z.h.p.HikariPool(fillPool):521 - HikariPool-2 - Fill pool skipped, pool has sufficient level or currently being filled (queueDepth=0).
2022-11-02 15:28:01 DEBUG o.f.c.i.l.s.Slf4jLog(debug):33 - Scanning for classpath resources at 'classpath:db/callback' ...
2022-11-02 15:28:01 DEBUG o.f.c.i.l.s.Slf4jLog(debug):33 - Determining location urls for classpath:db/callback using ClassLoader jdk.internal.loader.ClassLoaders$AppClassLoader@7a4f0f29 ...
2022-11-02 15:28:01 DEBUG o.f.c.i.l.s.Slf4jLog(debug):33 - Unable to resolve location classpath:db/callback.
2022-11-02 15:28:01 DEBUG o.f.c.i.l.s.Slf4jLog(debug):33 - Scanning for classpath resources at 'classpath:db/callback' ...
2022-11-02 15:28:01 DEBUG o.f.c.i.l.s.Slf4jLog(debug):33 - Determining location urls for classpath:db/callback using ClassLoader jdk.internal.loader.ClassLoaders$AppClassLoader@7a4f0f29 ...
2022-11-02 15:28:01 DEBUG o.f.c.i.l.s.Slf4jLog(debug):33 - Unable to resolve location classpath:db/callback.
2022-11-02 15:22:16 DEBUG i.a.c.h.LogClientSingleton(setWorkspaceMdc):150 - Setting kube workspace mdc
2022-11-02 15:22:16 ERROR i.a.s.ServerApp(main):326 - Server failed
java.lang.IllegalArgumentException: null
    at com.google.common.base.Preconditions.checkArgument(Preconditions.java:131) ~[guava-31.1-jre.jar:?]
    at io.airbyte.config.storage.DefaultS3ClientFactory.validateBase(DefaultS3ClientFactory.java:36) ~[io.airbyte.airbyte-config-config-models-0.40.17.jar:?]
    at io.airbyte.config.storage.DefaultS3ClientFactory.validate(DefaultS3ClientFactory.java:31) ~[io.airbyte.airbyte-config-config-models-0.40.17.jar:?]
    at io.airbyte.config.storage.DefaultS3ClientFactory.<init>(DefaultS3ClientFactory.java:24) ~[io.airbyte.airbyte-config-config-models-0.40.17.jar:?]
    at io.airbyte.config.helpers.CloudLogs.createCloudLogClient(CloudLogs.java:45) ~[io.airbyte.airbyte-config-config-models-0.40.17.jar:?]
    at io.airbyte.config.helpers.LogClientSingleton.createCloudClientIfNull(LogClientSingleton.java:164) ~[io.airbyte.airbyte-config-config-models-0.40.17.jar:?]
    at io.airbyte.config.helpers.LogClientSingleton.setWorkspaceMdc(LogClientSingleton.java:151) ~[io.airbyte.airbyte-config-config-models-0.40.17.jar:?]
    at io.airbyte.server.ServerApp.getServer(ServerApp.java:174) ~[io.airbyte-airbyte-server-0.40.17.jar:?]
    at io.airbyte.server.ServerApp.main(ServerApp.java:323) ~[io.airbyte-airbyte-server-0.40.17.jar:?]
2022-11-02 15:22:16 INFO c.z.h.HikariDataSource(close):350 - HikariPool-1 - Shutdown initiated...

this is to do with it still requiring access keys for logging, I’m working on a PR hitting the same issue

Hey @Nikita Nazarov, sorry for the delay, we’ve been experiencing a large influx of user questions and are working hard to reply to everyone. Were you able to upgrade to the latest using helm? It’s been a bit unstable recently.

@Saj Dider (Airbyte) +1 for getting this error. It's not just helm, I believe the kustomize is unstable as well

Hello Nikita Nazarov, it's been a while without an update from us. Are you still having problems or did you find a solution?