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
LiteLLM returned HTTP 401 for a credential resolved from /data/secrets/litellm_api_key. key_changed_since_start=false means the resolved key matched the first key this process saw; it does not show that Hive ignored a replacement.
The reported build (bb85cd0) and v5 both contain merged PR #18540 (re-read the key after a 401 and retry once if it changed) and merged PR #18557 (classify repeated upstream 401s as an operator credential issue). This report does not show a recurrence of the key-caching defect.
The spoke owner needs to verify that the configured key is valid for the reported LiteLLM endpoint, replace it at the effective source if needed, and confirm a reviewer inference request succeeds. Please do not share the key here.
/hive decision <your instructions>: go ahead, following your instructions
/hive help: show these again
If what this issue waited on has been done (a merged fix, or an action taken outside this repository), a maintainer can reply /fixed to close it as completed; Hive clears its park labels.
Closing: this is a spoke credential problem, not a Hive defect. The LiteLLM key configured on that spoke is being rejected (401); the running build already re-reads the key file after a 401 (#18540) and reports repeated 401s as an operator credential issue (#18557). The spoke owner needs to install a valid key; no Hive change is needed.
Activity
hivecommons-hive commentedon Nov 19, 2026
🔓 Claim by @Karibhou released (lease revoked).
Claim history
Karibhou(contributor on hive hosted-available-oke-11-placeholder-r05x)Karibhou(contributor; lease revoked)Karibhou commentedon Nov 19, 2026
LiteLLM returned HTTP 401 for a credential resolved from
/data/secrets/litellm_api_key.key_changed_since_start=falsemeans the resolved key matched the first key this process saw; it does not show that Hive ignored a replacement.The reported build (
bb85cd0) andv5both contain merged PR #18540 (re-read the key after a 401 and retry once if it changed) and merged PR #18557 (classify repeated upstream 401s as an operator credential issue). This report does not show a recurrence of the key-caching defect.The spoke owner needs to verify that the configured key is valid for the reported LiteLLM endpoint, replace it at the effective source if needed, and confirm a reviewer inference request succeeds. Please do not share the key here.
-- hive: backend=omp model=openai-codex/gpt-6.2-sol
hivecommons-hive commentedon Nov 19, 2026
What to reply
/hive approve: go with the recommendation/hive decision <your instructions>: go ahead, following your instructions/hive help: show these againIf what this issue waited on has been done (a merged fix, or an action taken outside this repository), a maintainer can reply
/fixedto close it as completed; Hive clears its park labels.Only a maintainer with write access can un-park; everything else is ignored. Full command reference: https://github.com/hivecommons/hive/blob/v5/src/docs/maintainer-commands.md.
clubanderson commentedon Nov 19, 2026
Closing: this is a spoke credential problem, not a Hive defect. The LiteLLM key configured on that spoke is being rejected (401); the running build already re-reads the key file after a 401 (#18540) and reports repeated 401s as an operator credential issue (#18557). The spoke owner needs to install a valid key; no Hive change is needed.