Hey, I am trying to run the latest datahub stack (

v0.8.10

) on Kubernetes using https://github.com/acryldata/datahub-helm/tree/master/charts/datahub But both

GMS

and

upgrade-job

pods have troubles running -> they both log errors showing that the main process cannot find

entity-registry.yml

file, e.g.:

10:46:49.006 [main] ERROR o.s.web.context.ContextLoader - Context initialization failed
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'metadataAuditEventsProcessor' defined in URL [jar:file:/tmp/jetty-0_0_0_0-8080-war_war-_-any-1391980781119123614.dir/webapp/WEB-INF/lib/mae-consumer.jar!/com/linkedin/metadata/kafka/MetadataAuditEventsProcessor.class]: Uns
atisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'searchServiceFactory': Unsatisfied dependency expressed through field 'elasticSearchService'; nested exception is org.springframework.beans
.factory.UnsatisfiedDependencyException: Error creating bean with name 'elasticSearchServiceFactory': Unsatisfied dependency expressed through field 'entityRegistry'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'entityRegistryFactory': Unsatisfied
 dependency expressed through field 'configEntityRegistry'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'configEntityRegistry' defined in com.linkedin.gms.factory.entityregistry.ConfigEntityRegistryFactory: Bean instantiation via factory method failed; nes
ted exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.linkedin.metadata.models.registry.ConfigEntityRegistry]: Factory method 'getInstance' threw exception; nested exception is java.io.FileNotFoundException: ../../metadata-models/src/main/resources/entity-registry.yml (No su
ch file or directory)
        at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:798)
(...)
Caused by: 
org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.linkedin.metadata.models.registry.ConfigEntityRegistry]: Factory method 'getInstance' threw exception; nested exception is java.io.FileNotFoundException: ../../metadata-models/src/main/resources/entity-registry.yml (No such file or direct
ory)

Are published images broken and we should maintain our own builds?

Hey @rhythmic-london-44496, Is your ElasticSearch service/pod is up & running?

yes, they are ->

elasticsearch-master-0                             1/1     Running     0          
elasticsearch-master-1                             1/1     Running     0          
elasticsearch-master-2                             1/1     Running     0
datahub-elasticsearch-setup-job-9vt7p              0/1     Completed   0          113m

Ops, I missed the entity-registry part. Could you please share your

ENTITY_REGISTRY_CONFIG_PATH

environment variable in your pod ?

hmmm, that's strange I don't have this entry in my deployment - shouldn't it be automatically populated with value from

charts/datahub/subcharts/datahub-gms/templates/deployment.yaml

?

Actually, it’s defined in this path as well. https://github.com/acryldata/datahub-helm/blob/master/charts/datahub/subcharts/datahub-gms/templates/deployment.yaml#L82-L83 Maybe, it’s caused by the steps you follow. I’m not sure. But, I can say that, I’ve upgraded the helm deployment via the following command.

helm upgrade datahub datahub/datahub --version 0.8.10

Hmm, I've tried to just install it anew using:

helm install datahub datahub/datahub --values charts/datahub/quickstart-values.yaml

and it didn't work. But you are right, it was about the variable 🙏

@rhythmic-london-44496 Did you change quickstart-values.yaml? I would suggest trying

helm repo remove datahub

and then readding it! Seems like it’s not picking up the latest subcharts

@early-lamp-41924 yep, I did. Yeah, sounds like that might work 😉