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
Regression: the runtime corporate CA merge was reported working in v0.0.81; it is absent in v0.0.102. Related public issue: #6210.
Description
NemoClaw accepts a restricted corporate CA certificate during onboarding and reports the sandbox Ready, but the managed corporate CA material and merged runtime trust bundle are absent inside the sandbox. Applications therefore cannot use the configured corporate trust anchor through the managed runtime contract.
Platform scope: Reproduced on Ubuntu 24.04 only; other platforms not tested.
Confirm nemoclaw ca-merge-check status reports the sandbox Ready.
Run:
nemoclaw ca-merge-check exec -- sh -c 'test -f /usr/local/share/nemoclaw/corporate-ca.pem; echo CORPORATE_CA_EXIT:$?; test -f /run/nemoclaw/managed-startup-ca-bundle.pem; echo MERGED_CA_EXIT:$?; printf "SSL_CERT_FILE=%s\n" "$SSL_CERT_FILE"'
Expected Result
Onboarding installs the validated corporate CA as root-owned, read-only managed material, creates a merged OpenShell and corporate CA bundle, and points SSL_CERT_FILE and the other managed CA environment variables at that merged bundle.
Actual Result
Onboarding exits successfully and the sandbox reaches Ready, but both managed CA files are absent. Both file checks exit 1, so the configured corporate CA is not available through the documented runtime trust contract.
Logs
$ nemoclaw ca-merge-check status
Sandbox: ca-merge-check
Phase: Ready
$ nemoclaw ca-merge-check exec -- sh -c 'test -f /usr/local/share/nemoclaw/corporate-ca.pem; echo CORPORATE_CA_EXIT:$?; test -f /run/nemoclaw/managed-startup-ca-bundle.pem; echo MERGED_CA_EXIT:$?'
CORPORATE_CA_EXIT:1
MERGED_CA_EXIT:1
Warning
Regression: the runtime corporate CA merge was reported working in v0.0.81; it is absent in v0.0.102. Related public issue: #6210.
Description
NemoClaw accepts a restricted corporate CA certificate during onboarding and reports the sandbox Ready, but the managed corporate CA material and merged runtime trust bundle are absent inside the sandbox. Applications therefore cannot use the configured corporate trust anchor through the managed runtime contract.
Platform scope: Reproduced on Ubuntu 24.04 only; other platforms not tested.
Environment
Steps to Reproduce
Prepare a valid CA certificate at
/var/tmp/corporate-ca.crtand set its mode to0600.Run:
Confirm
nemoclaw ca-merge-check statusreports the sandbox Ready.Run:
Expected Result
Onboarding installs the validated corporate CA as root-owned, read-only managed material, creates a merged OpenShell and corporate CA bundle, and points
SSL_CERT_FILEand the other managed CA environment variables at that merged bundle.Actual Result
Onboarding exits successfully and the sandbox reaches Ready, but both managed CA files are absent. Both file checks exit 1, so the configured corporate CA is not available through the documented runtime trust contract.
Logs