opschain admin agent rollover finish
packs:agentspacks:agent-governance
opschain admin agent rollover finish <agent> [--lane <lane>] [--reason <text>] [--server <url>] [--auth-token <token>]
Close a completed rollover and offer the source release for retirement (v2 AgentService.AdvanceAgentRollover, action finish).
Applies once every instance of the lane re-enrolled from the target
release (completed): the rollover closes as finished, lands
info:agent:rollover_finished, and the command offers the source
release for retirement by printing opschain admin agent-release retire <name>@<version> — the retirement is never run automatically.
Under blue-green it applies after the flip (flipped) and retires
the old lane: each old instance is drained, halted with a typed reason
naming the rollover (lane retired by rollover <id>: lane "<green>" retired, stop this process — the process reports the halt and never
serves again; stop it) and its instance row retired (listed retired by
admin agent instances), attested instance_retired one by one; then
the source release is offered for retirement as above.
Every step is attested on the release (opschain admin agent-release show) under the rollover's one correlation chain. <agent> is the
agent's member id, <project>/<code>, or a bare code when exactly one
project holds it; --lane names the lane whose open rollover the verb
applies to.
Flags
| Flag | Meaning |
|---|---|
--lane <lane> | The lane whose open rollover the verb applies to (default stable). |
--reason <text> | Audited reason. |
--server <url> | Server base URL. Default: the active context, then OPSCHAIN_SERVER. |
--auth-token <token> | Admin bearer token override. Default: your opschain login session, then $OPSCHAIN_ADMIN_TOKEN, then the token stored by opschain admin login for that server. |
Output
rollover 01a1aecc-… of limebank/felix lane stable: finished (felix@2.0.0 → felix@2.1.0)
-o json|yaml prints the rollover document; the status becomes
finished.
Exit codes
| Code | Meaning |
|---|---|
| 0 | The verb applied. |
| 1 | The server refused it: no rollover is open on the lane, or the rollover is not in a state the verb applies to (the message names the state). |
| 2 | Usage — wrong arguments, or no server / admin token resolvable. |
See also
opschain docs cli/admin-agent-rollover— the rollover verb and its strategies.