Issue with Airbyte worker after updating to 0.50.44

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

Summary

Enum constant error in Airbyte worker after updating to version 0.50.44


Question

Hi folks - seeing an issue with airbyte worker after updating to 0.50.44:

Message: No enum constant io.airbyte.config.storage.CloudStorageConfigs.WorkerStorageType.
Path Taken: new ApplicationInitializer() –> ApplicationInitializer.checkConnectionActivities –> List.checkConnectionActivities([CheckConnectionActivity checkConnectionActivity]) –> new CheckConnectionActivityImpl(WorkerConfigsProvider workerConfigsProvider,ProcessFactory processFactory,SecretsRepositoryReader secretsRepositoryReader,Path workspaceRoot,WorkerEnvironment workerEnvironment,[LogConfigs logConfigs],AirbyteApiClient airbyteApiClient,String airbyteVersion,AirbyteMessageSerDeProvider serDeProvider,AirbyteProtocolVersionedMigratorFactory migratorFactory,FeatureFlags featureFlags,FeatureFlagClient featureFlagClient,GsonPksExtractor gsonPksExtractor,WorkloadApi workloadApi,WorkloadIdGenerator workloadIdGenerator,JobOutputDocStore jobOutputDocStore) –> new LogConfigs([Optional storageConfigs])
at io.micronaut.context.DefaultBeanContext.resolveByBeanFactory(DefaultBeanContext.java:2367) ~[micronaut-inject-3.10.1.jar:3.10.1]
at io.micronaut.context.DefaultBeanContext.doCreateBean(DefaultBeanContext.java:2305) ~[micronaut-inject-3.10.1.jar:3.10.1]
at io.micronaut.context.DefaultBeanContext.doCreateBean(DefaultBeanContext.java:2251) ~[micronaut-inject-3.10.1.jar:3.10.1]
at io.micronaut.context.DefaultBeanContext.createRegistration(DefaultBeanContext.java:3016) ~[micronaut-inject-3.10.1.jar:3.10.1]
at io.micronaut.context.SingletonScope.getOrCreate(SingletonScope.java:80) ~[micronaut-inject-3.10.1.jar:3.10.1]
at io.micronaut.context.DefaultBeanContext.findOrCreateSingletonBeanRegistration(DefaultBeanContext.java:2918) ~[micronaut-inject-3.10.1.jar:3.10.1]
at io.micronaut.context.DefaultBeanContext.resolveBeanRegistration(DefaultBeanContext.java:2879) ~[micronaut-inject-3.10.1.jar:3.10.1]
at io.micronaut.context.DefaultBeanContext.resolveBeanRegistration(DefaultBeanContext.java:2800) ~[micronaut-inject-3.10.1.jar:3.10.1]
at io.micronaut.context.DefaultBeanContext.findBean(DefaultBeanContext.java:1680) ~[micronaut-inject-3.10.1.jar:3.10.1]
at io.micronaut.context.AbstractBeanResolutionContext.findBean(AbstractBeanResolutionContext.java:84) ~[micronaut-inject-3.10.1.jar:3.10.1]
at io.micronaut.context.AbstractInitializableBeanDefinition.resolveOptionalBean(AbstractInitializableBeanDefinition.java:2178) ~[micronaut-inject-3.10.1.jar:3.10.1]


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

["airbyte-worker", "update", "enum-constant-error", "version-0.50.44"]
2

<@U06FUELHQMN> please use threads.

3

Apologies <@U01MMSDJGC9>!

4

seems like the enum is actually there - and I’ve tried a good few different combinations (local, s3, minio etc for the WORKER_LOGS_STORAGE_TYPE and WORKER_STATE_STORAGE_TYPE) to no avail.

5

Message: No enum constant io.airbyte.config.storage.CloudStorageConfigs.WorkerStorageType.LOCAL for example is so odd - I can see the enum there, and the environment variable is set. Any ideas?

6

From what version did you upgrade from <@U06FUELHQMN>?

7

My env file and docker-compose yml are both the same as the ones currently in main in airbyte-platform

8

I cleared down all the images, containers and volumes and restarted, but same issue. I’m using an external Postgres DB for the airbyte DB - so there may be some data lying around in there related to the upgrade from 0.44.1

9

Did you retrieve the flags.yaml file as well?

10

I’m also experiencing this any updates?

11

<@U06ACAECS2G> and <@U06FUELHQMN> are you using external S3 logs in Helm or Docker?

12

Nope, I was just using local. I managed to resolve this - turned out there was actually a formatting issue in the .env file - there were some characters that weren’t showing up in my editor causing weirdness. It’s working now

13

<@U06ACAECS2G>
• what does your .env file look like? If it’s the same issue as mine, check that your WORKER_LOGS_STORAGE_TYPE and WORKER_STATE_STORAGE_TYPE env var values don’t have any characters at the end
• What version of airbyte are you running
• On the flags thing - I had to update the path to flags to be an absolute path

14

Hi <@U06FUELHQMN>, I upgraded to the latest release tag 0.50.47 and that solved the problem Message: No enum constant io.airbyte.config.storage.CloudStorageConfigs.WorkerStorageType in my case.

15

Hello Nithin and Martin, please take a look in https://github.com/airbytehq/airbyte/pull/34621 maybe there is some help there

16

yep, it’s there too - alongside the docker-compose.yml and .env

17

oh wait - does it have to be inside the configs folder?

18

ohhh

2024-01-24 14:17:31 INFO i.a.f.ConfigFileClient(&lt;init&gt;):105 - path /flags does not exist, will return default flag values

19

from the server logs

20

updated the path but the worker is still throwing the error about the missing enum unfortunately