#logging-issue
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2528 issues
When running `openclaw update`, the **Completion cache update** step produces the following error: ``` Completion cache update failed ([openclaw] Failed to start CLI: Error: qa scenario pack not found: qa/scenarios/index.md at readQaScenarioPack (file:///usr/local/lib/node_modules/openclaw/dist/suite-BW4kSK9C.js:754:27) at readQaScenarioById (file:///usr/local/lib/node_modules/openclaw/dist/suite-BW4kSK9C.js:790:19) at readQaScenarioExecutionConfig (file:///usr/local/lib/node_modules/openclaw/dist/suite-BW4kSK9C.js:795:9) at readRequiredDiscoveryRefs (file:///usr/local/lib/node_modules/openclaw/dist/suite-BW4kSK9C.js:2834:9) at file:///usr/local/lib/node_modules/openclaw/dist/suite-BW4kSK9C.js:2840:39 ```
openclaw onboard --mode local --no-install-daemon fails before entering onboarding with loadFacadeModule(...).shouldNormalizeGoogleProviderConfig is not a function, while node dist/index.js onboard --mode local --no-install-daemon enters the wizard successfully under the same installation.
After a gateway restart following the 2026.4.1 update, the local node-host service requests a role-upgrade repair pairing (roleFrom=operator roleTo=node). This creates an unresolvable deadlock: openclaw devices list works (uses local fallback) openclaw devices approve <requestId> returns unknown requestId — no local fallback path openclaw doctor --fix does not detect or resolve the pending request The Control UI dashboard shows no pending pairing request to approve via UI All CLI commands requiring gateway auth fail with 1008: pairing required The result is a fully locked gateway that cannot be recovered through any supported CLI path.
When spawning a subagent with `sessions_spawn` using an NVIDIA provider configured as `"api": "openai-completions"`, OpenClaw sends Anthropic-style message content (arrays with `type` objects) instead of OpenAI-style simple strings. This causes the NVIDIA API to reject requests with HTTP 400 errors. bug was created using openclaw *
OpenClaw 2026.3.8 (3caab92) Setup Mac node host via SSH tunnel to local gateway Worker: 127.0.0.1:18791 → Gateway: 127.0.0.1:18789 Confirmed - tunnel works (nc -vz 127.0.0.1 18791 succeeds) - worker node service runs - worker has ~/.openclaw/identity/device.json - worker never creates ~/.openclaw/identity/device-auth.json Gateway behavior gateway logs show: device pairing auto-approved device=df72580fdf4e6ddf4a8635f50ecc2c23870a247ab1e0608feef328e4be1be34c role=node Node runtime state: Known: 1 · Paired: 0 · Connected: 1 Research Node ... unpaired · connected Device store: openclaw devices list --json { "pending": [], "paired": [ { "nodeId": "cb91b74b0afad0605fb8725ec991d86cccd24b3e059a73966a902778e19a8156" } ] } So the node reaches the runtime registry but never enters the persistent device pairing store and never writes device-auth.json. Question Why does WS node pairing auto-approve at runtime but never persist to devices pending/paired or create device-auth.json on the worker? 'Known: 1 · Paired: 0 · Connected: 1 Research Node ... unpaired · connected'
There are five related bugs in the Anthropic `/v1/messages` experimental pass-through implementation when routing requests to OpenAI/Azure models. These issues were discovered during integration testing with Claude Code CLI which uses `input_text` content block format and requires forcing routing through Chat Completions API when the downstream proxy doesn't support Responses API.
When configuring multiple Ollama providers (`ollama` on port 11434 and `ollama2` on port 11435), the Gateway routes ALL requests to the first provider (`ollama` on port 11434), completely ignoring the `baseUrl` configured for `ollama2`.