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
The nvidia inference provider type produces 404 errors from the NVIDIA Build API because of URL path duplication. The provider's default base_url is https://integrate.api.nvidia.com/v1, and the router appends the request path /v1/chat/completions, resulting in https://integrate.api.nvidia.com/v1/v1/chat/completions (double /v1).
The openai provider type works correctly with the same URL pattern, so the path deduplication logic works for OpenAI but not for NVIDIA.
Root Cause
The bug is in crates/openshell-router/src/backend.rs where the upstream URL is constructed by combining the route's endpoint (base URL) with the request path. The path deduplication that strips the /v1 prefix works for the OpenAI provider but does not apply to the NVIDIA provider.
Deployed in SAW (Secure Agent Workspace) on OpenShift 4.22.8
Agent Diagnostic
Confirmed direct API access works with curl (valid 200 response from meta/llama-3.3-70b-instruct)
Traced the routing path: supervisor proxy -> gateway GetInferenceBundle -> router -> NVIDIA API
Identified the URL construction in crates/openshell-router/src/backend.rs as the source of the duplication
The OpenAI provider handles the same pattern correctly, indicating the fix should extend the existing deduplication logic to cover the NVIDIA provider type
The /v1 deduplication in build_backend_url() at crates/openshell-router/src/backend.rs:822-847 handles NVIDIA and OpenAI identically. Both providers use the same code path ((None, false) arm), share OPENAI_PROTOCOLS, and the existing test at line 996 already covers this URL pattern.
The 404 I experienced during the SAW deployment was real, but the cause was likely:
A stale inference bundle (the provider was recreated multiple times during debugging)
The sandbox using a cached route from a prior provider configuration
Or a transient API key scope issue on the NVIDIA Build API side
Activity
rhuss commentedon Aug 9, 2026
Closing: the root cause claim was wrong.
The
/v1deduplication inbuild_backend_url()atcrates/openshell-router/src/backend.rs:822-847handles NVIDIA and OpenAI identically. Both providers use the same code path ((None, false)arm), shareOPENAI_PROTOCOLS, and the existing test at line 996 already covers this URL pattern.The 404 I experienced during the SAW deployment was real, but the cause was likely:
The router code is correct. No fix needed.