In productionProbeginnerNamespace
The action server cannot be found
Reconnect the mission client to Nav2 without removing the robot namespace.
Pairs with Nodes, names, and namespaces in ROS 2 Systems Debugging. Read the concept first, then diagnose it here.
Unlock this lab with ProOperator report
The client waits for `/navigate_to_pose`, while the server is visible under `/robot_1/navigate_to_pose`.
Ubuntu 24.04, ROS 2 Jazzy, Python and C++ nodes, browser telemetry workspace
System boundary
Trace only the relevant path.
mission_client/navigate_to_poseNav2 action server
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.
- Action server discovered
- Goal accepted
- Hidden regression behavior
- Root cause explanation