You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Affected module
Does it impact the UI, backend or Ingestion Framework?
Impacts the UI and Server. Server fails to start.
Describe the bug
A clear and concise description of what the bug is.
Below is the error I see in catalog.err file that openmetadata generates -
org.openmetadata.catalog.exception.EntityNotFoundException: Entity type role not found
at org.openmetadata.catalog.exception.EntityNotFoundException.byMessage(EntityNotFoundException.java:42)
at org.openmetadata.catalog.Entity.getEntityReferenceById(Entity.java:131)
at org.openmetadata.catalog.util.EntityUtil.populateEntityReferences(EntityUtil.java:241)
at org.openmetadata.catalog.jdbi3.UserRepository.getRoles(UserRepository.java:200)
at org.openmetadata.catalog.jdbi3.UserRepository.setFields(UserRepository.java:138)
at org.openmetadata.catalog.jdbi3.UserRepository.setFields(UserRepository.java:43)
at org.openmetadata.catalog.jdbi3.EntityRepository.createOrUpdate(EntityRepository.java:389)
at org.openmetadata.catalog.jdbi3.EntityRepository.createOrUpdate(EntityRepository.java:374)
at org.openmetadata.catalog.security.DefaultAuthorizer.addOrUpdateUser(DefaultAuthorizer.java:251)
at org.openmetadata.catalog.security.DefaultAuthorizer.mayBeAddAdminUsers(DefaultAuthorizer.java:87)
at org.openmetadata.catalog.security.DefaultAuthorizer.init(DefaultAuthorizer.java:63)
at org.openmetadata.catalog.CatalogApplication.registerAuthorizer(CatalogApplication.java:184)
at org.openmetadata.catalog.CatalogApplication.run(CatalogApplication.java:103)
at org.openmetadata.catalog.CatalogApplication.run(CatalogApplication.java:69)
at io.dropwizard.cli.EnvironmentCommand.run(EnvironmentCommand.java:59)
at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:98)
at io.dropwizard.cli.Cli.run(Cli.java:78)
at io.dropwizard.Application.run(Application.java:94)
at org.openmetadata.catalog.CatalogApplication.main(CatalogApplication.java:239)
To Reproduce
maven build from main branch --> untar the binary --> run bootstrap migrate --> run the server in insecure mode --> Update the config to add authentication/authorisation config via environment variable --> restart the server to run in secure mode --> FAILS.
maven build from main branch --> untar the binary --> run bootstrap migrate --> run the server in insecure mode --> Ingest sample data --> stop the server --> update the config to add authentication/ authorisation config via environment variable --> start the server to run in secure mode --> FAILS.
Expected behavior
Open Metadata server should start with config changes from environment variables.
Version:
OS: Ubuntu
OpenMetadata version: main branch
OpenMetadata Ingestion package version: main branch
Additional context
Work Around here is to run bootstrap_storage.sh drop-create-all. But that is not ideal in production environment.
Affected module
Does it impact the UI, backend or Ingestion Framework?
Impacts the UI and Server. Server fails to start.
Describe the bug
A clear and concise description of what the bug is.
Below is the error I see in catalog.err file that openmetadata generates -
To Reproduce
maven build from main branch --> untar the binary --> run bootstrap migrate --> run the server in insecure mode --> Update the config to add authentication/authorisation config via environment variable --> restart the server to run in secure mode --> FAILS.
maven build from main branch --> untar the binary --> run bootstrap migrate --> run the server in insecure mode --> Ingest sample data --> stop the server --> update the config to add authentication/ authorisation config via environment variable --> start the server to run in secure mode --> FAILS.
Expected behavior
Open Metadata server should start with config changes from environment variables.
Version:
Additional context
Work Around here is to run
bootstrap_storage.sh drop-create-all
. But that is not ideal in production environment.cc- @darth-coder00 , @harshach
The text was updated successfully, but these errors were encountered: