Skip to main content
Version: v5.6.1

opschain admin agent rollover rollback

packs:agentspacks:agent-governance

opschain admin agent rollover rollback <agent> [--lane <lane>] [--reason <text>] [--server <url>] [--auth-token <token>]

Return every instance of the lane to the source release (v2 AgentService.AdvanceAgentRollover, action rollback).

Applies after continue (or to a replace rollover, rolling or completed): every instance that moved to the target release is drained and instructed to restart from the source release; the rollover closes as rolled_back once the last one re-enrols. Lands info:agent:rollover_rolled_back. While the canaries still hold, use abort.

Under blue-green it applies after the flip (flipped) and is the flip back: the same one-write relabel in reverse — the old instances take the serving label and every new dispatch again, the green instances return to the green lane's name — and the rollover closes as rolled_back. The green lane keeps its instances on the target release: stop them, or roll over again and they count at once.

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​

FlagMeaning
--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: rolling_back (felix@2.0.0 → felix@2.1.0)

-o json|yaml prints the rollover document; the status becomes rolling_back, then rolled_back.

Exit codes​

CodeMeaning
0The verb applied.
1The 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).
2Usage — wrong arguments, or no server / admin token resolvable.

See also​

  • opschain docs cli/admin-agent-rollover — the rollover verb and its strategies.