Description

Description
PR #3039 specifies that nemoclaw onboard on Linux must actively configure (or repair) a systemd drop-in at /etc/systemd/system/ollama.service.d/override.conf pinning OLLAMA_HOST to 127.0.0.1:11434, and must print a "Configuring Ollama systemd loopback override..." line in the onboard transcript. On v0.0.38 against a fresh Ollama install on a Brev Ubuntu 22.04 VM, the wizard does not print that line and the drop-in file is never created. The wizard appears to short-circuit when it sees Ollama already bound to 127.0.0.1 and skip both the message and the file write. The skip is silent. The gap matters because if a future package update or sysadmin change widens the bind to 0.0.0.0, the drop-in is the mechanism that pins it back — without it, the loopback guarantee depends on the upstream installer default never changing.

Environment

Device:        Brev VM (shadeform brev-pz811qnfg)
OS:            Ubuntu 22.04.5 LTS
Architecture:  x86_64
Node.js:       v22.22.2
npm:           10.9.7
Docker:        29.1.3 (build f52814d)
OpenShell CLI: openshell 0.0.36
NemoClaw:      v0.0.38
OpenClaw:      2026.4.24
Ollama:        0.23.2 (default install, bound 127.0.0.1:11434)

Steps to Reproduce

1. Fresh Brev Ubuntu 22.04 VM with no Ollama installed and no NemoClaw installed.
2. Install Ollama with the upstream script (no overrides): curl -fsSL https://ollama.com/install.sh | sh
3. Pull a tiny model: ollama pull qwen2.5:0.5b
4. Confirm Ollama defaults to loopback: ss -tlnp | grep 11434  -> 127.0.0.1:11434
5. Install NemoClaw: curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash
6. At [3/8] inference menu, select option 7 "Local Ollama (localhost:11434) — running (suggested)".
7. After onboard completes, inspect:
     ls -la /etc/systemd/system/ollama.service.d/
     grep -iE 'loopback override|OLLAMA_HOST=127' /tmp/install.log

Expected Result

After onboard, /etc/systemd/system/ollama.service.d/override.conf exists with a [Service] block setting Environment="OLLAMA_HOST=127.0.0.1:11434", and the onboard transcript includes a "Configuring Ollama systemd loopback override..." line confirming the drop-in was applied or refreshed. The bind remains on 127.0.0.1 after the drop-in is applied.

Actual Result
The drop-in directory is not created and the confirmation line is never logged:

$ ls -la /etc/systemd/system/ollama.service.d/
ls: cannot access '/etc/systemd/system/ollama.service.d/': No such file or directory

$ grep -iE 'loopback override|OLLAMA_HOST=127' /tmp/install.log
(no matching line)

Ollama's bind happens to be 127.0.0.1 because the upstream installer's default already pins it there, but NemoClaw never registered the explicit override per the PR #3039 design.

Bug Details

Field	Value
Priority	Unprioritized
Action	Dev - Open - To fix
Disposition	Open issue
Module	Machine Learning - NemoClaw
Keyword	NemoClaw, NEMOCLAW_GH_SYNC_APPROVAL, NemoClaw_Onboard, NemoClaw_Security

---

[NVB#6164263]