Resume, recover, and roll back
Continue a failed registration, reconcile local state, or roll back checkpoints
Registration is checkpointed on the agent VM under ~/.nr/. If a run fails mid-way, you usually resume instead of starting over.
Resume after a failure
Use the same agent name (and the same major flags you care about):
nr cluster register --resume --name edge-ams-01Typical reasons to resume:
- Network blip while downloading tools or charts
- Temporary API error
- Operator credentials were missing on the first attempt
Inspect where you left off:
nr cluster status --name edge-ams-01
nr cluster info --name edge-ams-01Re-run the operator phase only
If peering succeeded but the operator Helm install needs another pass (chart or image fix):
nr cluster register \
--resume \
--name edge-ams-01 \
--reinstall-operator \
--yes--reinstall-operator and --skip-operator-install are mutually exclusive.
Recover local state
If the cluster looks installed but local checkpoints are wrong or incomplete:
nr cluster recover --name edge-ams-01Recover reconciles local state with what is actually present on the machine.
Roll back checkpoints
Roll installation state back to the last successful checkpoint (does not always uninstall every package):
nr cluster rollback --name edge-ams-01Reset checkpoints (keep agent identity)
Clear checkpoints while keeping the agent ID/name association:
nr cluster reset --name edge-ams-01Use this when you intentionally want register to treat phases as pending again without deleting the API agent.
When to deregister instead
If the VM is disposable or the install is badly corrupted, deregister uninstalls local components and can delete the agent from the API. Prefer resume/recover for transient failures.