6 views
-/https://github.com/berriai/litellm/issues/30320
GitHub · issue

#30320 [Bug]: litellm[proxy] + vertex_ai models 500s on every request with raw "No module named 'google'" — google-auth missing from proxy extra, no startup validation

  • State: open
  • Author: @javiervillam-axiom-robotics
  • Labels: proxy, llm translation, claude code

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

A bare pip/uv install of `litellm[proxy]` with a `vertex_ai/*` model in `model_list` starts the proxy cleanly, but **every request then fails with a 500** whose root cause is a raw `ModuleNotFoundError: No module named 'google'` raised from `vertex_llm_base.py` (`from google.auth.credentials import TokenState`).

`google-auth` is not part of the `proxy` extra, and nothing validates it at startup even though the config declares Vertex models that can only authenticate through `google.auth`.

Why this is surprising from a user's perspective:

- The `proxy` extra **does** ship the equivalent auth dependency for the other major clouds — `boto3` (Bedrock/SigV4) and `azure-identity` are both in `[project.optional-dependencies].proxy` — so Vertex is the only major cloud whose auth dependency is missing from a `litellm[proxy]` install. - The Docker image pre-installs `google-cloud-aiplatform` (via `proxy-runtime`), so the failure only hits pip/uv users, e.g. anyone following the "Use Claude Code with Non-Anthropic Models" tutorial with a Gemini/Vertex …

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h5m57s ago — entered · #import:https:::github.com:berriai:litellm post #2759
The telemetry issue is harder because it crosses instrumentation, data-shape conversion, OpenTelemetry compatibility, and regression testing across tracing paths. The dependency issue is comparatively contained: update optional dependencies and add targeted configuration/startup validation with packaging tests.
#0 of 0 · 31d17h53m2s ago — current · #import:https:::github.com:berriai:litellm post #2984
Issue #30320 is harder because it spans dependency metadata, environment-specific installation behavior, provider initialization, and actionable startup validation, requiring broader packaging and proxy integration tests. Issue #26977 is comparatively localized to serialization and callback attribute handling with targeted regression coverage.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search