Skip to main content
Version: v5.7.0

opschain admin agent rollover show

packs:agents

opschain admin agent rollover show <agent> [--lane <lane>] [--id <rollover>] [--server <url>] [--auth-token <token>]

Shows the lane's open rollover — or, with --id, any rollover by id — together with the lanes it concerns and which one dispatch addressing the rolled lane lands on (v2 AgentService.GetAgentRollover + ListAgentInstances). Every strategy renders its rolled lane; a blue-green rollover renders its green lane beside it: before the flip the green lane holds the target release's instances and serves nothing, after it the serving label names the target release's instances and the green lane's name the old ones, parked for rollback until finish.

<agent> is the agent's member id, <project>/<code>, or a bare code when exactly one project holds it.

Flags​

FlagMeaning
--lane <lane>The lane whose open rollover to show (default stable).
--id <rollover>A rollover id (any state) instead of the lane's open one.
--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 01a1b370-… of limebank/felix lane stable: felix@2.0.0 → felix@2.1.0 (blue-green), status flipped
requested by priya at 2026-11-07T10:00:00Z; updated 2026-11-07T10:05:00Z
green lane stable-green, size 2, 2 up
lane stable: serving — felix@2.1.0, 2 instance(s), 2 online [01a1b370-4e5d-… 01a1b370-4e68-…]
lane stable-green: parked (serves nothing) — felix@2.0.0, 2 instance(s), 2 online [01a1b370-46e3-… 01a1b370-472f-…]
chain 01a1b370-c4d0-…

A replace or canary rollover prints targets N, canaries N, restarted N, returned N in place of the green-lane line and its one lane. -o json|yaml prints the rollover document with a lanes array (lane, serving, release, instances, online).

Exit codes​

CodeMeaning
0The rollover was printed.
1The server refused or failed the request: no rollover is open on the lane (or the id is unknown), an unknown agent, a rejected credential.
2Usage — wrong arguments, or no server / admin token resolvable.

See also​

  • opschain docs cli/admin-agent-rollover — the rollover verb and its strategies.
  • opschain docs cli/admin-agent-instances — every instance of the agent by release and lane.
  • opschain docs agent-releases — the rollover state machine.