In productionProbeginnerRelease identity
Two robots run different code under the same tag
Make deployed software identity immutable and auditable.
Pairs with Deployments and updates in Production ROS Operations. Read the concept first, then diagnose it here.
Unlock this lab with ProOperator report
Both robots report `botopsy/nav:latest`, but only one contains the controller fix.
Ubuntu 24.04, ROS 2 Jazzy, Cyclone DDS, containers, systemd, OpenTelemetry fleet sandbox
System boundary
Trace only the relevant path.
image registry tagresolved digestrobot deployment
How this lab works
You diagnose it — no command list.
Open the repair workspace and gather your own evidence in a real terminal. No diagnostic commands are handed to you — finding the fault is the exercise. Stuck? Progressive hints unlock inside the workspace.
Verification
Your repair must pass more than the visible symptom.
- Fleet reports one digest
- Release record includes provenance
- Hidden regression behavior
- Root cause explanation