In productionProbeginnerStartup readiness
The robot fails only at boot
Make drive startup wait for a usable CAN interface without a fixed sleep.
Pairs with systemd and startup order in Production ROS Operations. Read the concept first, then diagnose it here.
Unlock this lab with ProOperator report
Manual service restart works, but boot startup reports `can0 not found`.
Ubuntu 24.04, ROS 2 Jazzy, Cyclone DDS, containers, systemd, OpenTelemetry fleet sandbox
System boundary
Trace only the relevant path.
systemd network targetcan0 readinessdrive service
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.
- Cold boot starts drive
- Missing can0 fails clearly
- Hidden regression behavior
- Root cause explanation