Description
Description
nemoclaw onboard / install fails because the newly released openshell 0.0.38
is above the maximum (0.0.36) declared in this NemoClaw release's blueprint.
Install hard-stops with no upgrade path: the installer auto-fetches the latest
openshell, but the NemoClaw release pins max_openshell_version=0.0.36, so the
two are incompatible out of the box. This blocks fresh installs on any host
once openshell 0.0.38 is the "latest" tag — the user has no way around it
short of pinning openshell themselves.
Environment
Device: DGX Spark
OS: Ubuntu 24.04 LTS (aarch64)
Architecture: arm64
Node.js: v22.x
npm: 10.x
Docker: 28.x
OpenShell CLI: 0.0.38 (latest at time of install)
NemoClaw: v0.0.38
OpenClaw: N/A (install failed)
Steps to Reproduce
1. On a fresh DGX Spark (no prior nemoclaw / openshell), run:
curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash
2. Installer fetches openshell 0.0.38 (the current "latest").
3. Blueprint compatibility check (max_openshell_version=0.0.36) trips.
Expected Result
Either of:
(a) The NemoClaw release ships with max_openshell_version >= 0.0.38 so a fresh
install resolves a compatible pair; OR
(b) The installer pins openshell to <= max_openshell_version and refuses to
fetch newer releases, instead of fetching latest and then failing the
compatibility gate.
Actual Result
[install] openshell 0.0.38 is above the maximum (0.0.36) supported by this
NemoClaw release. Upgrade NemoClaw first.
Install exits 1.
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_Install |
[NVB#6168430]
Description
Description
Environment Steps to Reproduce Expected ResultEither of: (a) The NemoClaw release ships with max_openshell_version >= 0.0.38 so a fresh install resolves a compatible pair; OR (b) The installer pins openshell to <= max_openshell_version and refuses to fetch newer releases, instead of fetching latest and then failing the compatibility gate.Actual ResultBug Details
[NVB#6168430]