Containerized registry server fails on startup due to a ModuleNotFoundError #4729

Activity

1. tchughesiv

   added

   kind/bug

   priority/p2

   on Nov 1, 2024
2. tchughesiv

   changed the title [-]bug: Containerized registry server fails on startup due to a ModuleNotFoundError[/-] [+]Containerized registry server fails on startup due to a ModuleNotFoundError[/+] on Nov 1, 2024
3. ckavili commented on Nov 2, 2024

   

   ckavili

   on Nov 2, 2024

   Contributor

   More actions

   came here to raise the same issue for the latest version of the image but for the missing psycopg2 module.

   Received base64 encoded feature_store.yaml
   Traceback (most recent call last):
     File "/usr/local/bin/feast", line 8, in <module>
       sys.exit(cli())
     File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 1157, in __call__
       return self.main(*args, **kwargs)
     File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 1078, in main
       rv = self.invoke(ctx)
     File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 1688, in invoke
       return _process_result(sub_ctx.command.invoke(sub_ctx))
     File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 1434, in invoke
       return ctx.invoke(self.callback, **ctx.params)
     File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 783, in invoke
       return __callback(*args, **kwargs)
     File "/usr/local/lib/python3.9/dist-packages/click/decorators.py", line 33, in new_func
       return f(get_current_context(), *args, **kwargs)
     File "/usr/local/lib/python3.9/dist-packages/feast/cli.py", line 182, in ui
       store = create_feature_store(ctx)
     File "/usr/local/lib/python3.9/dist-packages/feast/repo_operations.py", line 383, in create_feature_store
       return FeatureStore(repo_path=str(repo_path.resolve()))
     File "/usr/local/lib/python3.9/dist-packages/feast/feature_store.py", line 151, in __init__
       self._registry = SqlRegistry(registry_config, self.config.project, None)
     File "/usr/local/lib/python3.9/dist-packages/feast/infra/registry/sql.py", line 256, in __init__
       self.write_engine: Engine = create_engine(
     File "<string>", line 2, in create_engine
     File "/usr/local/lib/python3.9/dist-packages/sqlalchemy/util/deprecations.py", line 281, in warned
       return fn(*args, **kwargs)  # type: ignore[no-any-return]
     File "/usr/local/lib/python3.9/dist-packages/sqlalchemy/engine/create.py", line 599, in create_engine
       dbapi = dbapi_meth(**dbapi_args)
     File "/usr/local/lib/python3.9/dist-packages/sqlalchemy/dialects/postgresql/psycopg2.py", line 690, in import_dbapi
       import psycopg2
   ModuleNotFoundError: No module named 'psycopg2'
   
4. tokoko commented on Nov 2, 2024

   

   tokoko

   on Nov 2, 2024

   Collaborator

   More actions

   @tchughesiv I don't think this is specific to grpc_health, looks like we are not installing grpc extra in the default image. I guess we can add it since we are relying on grpc more now with remote registry, although hard to decide which extras need to be included and which can be left out. I think we need to do something like #4379 to solve this properly.

   @ckavili What uri are you using with the sql registry? with sql registry the user is responsible for bringing in the dependencies needed for the sqlalchemy backend. Looks like you're using psycopg2 for registry backend, you need to bring that in yourself, feast[postgres] won't help here because feast postgres components (offline, online) depend on psycopg (psycopg3) instead. Alternatively you can switch to psycopg for the registry as well.
5. tokoko

   closed this as completedin #4737on Nov 5, 2024