Hi,
There is a bug in the current launch files for the Mission Client when using namespaces.
When launching the client with a namespace argument e.g
~/projects/isaac_mission$ ros2 launch isaac_ros_vda5050_nav2_client_bringup isaac_ros_vda5050_client.launch.py ros_namespace:='r0'
The nodes that are launched appear to heave their namespace applied twice.
[INFO] [vda5050_nav2_client-1]: process started with pid [208488] [INFO] [ros_to_mqtt_bridge_node-2]: process started with pid [208490] [INFO] [mqtt_to_ros_bridge_node-3]: process started with pid [208492] [mqtt_to_ros_bridge_node-3] [INFO] [1674476648.202187545] [r0.r0.mqtt_ros_bridge_node]: Connected with result code 0 [ros_to_mqtt_bridge_node-2] [INFO] [1674476648.212896233] [r0.r0.ros_mqtt_bridge_node]: Connected with result code 0
It appears that ros_namespace is a built in parameter for the ros_launch system. And that by using that name as the parameter the namespace gets applied twice.

Simply changing the parameter name fixes this issue - Below I have changed the ros_namespace parameter to be called namespace and it works fine:

~/projects/isaac_mission/src/isaac_ros_mission_client$ ros2 launch isaac_ros_vda5050_nav2_client_bringup isaac_ros_vda5050_client.launch.py namespace:='r0' [INFO] [vda5050_nav2_client-1]: process started with pid [213704] [INFO] [ros_to_mqtt_bridge_node-2]: process started with pid [213706] [INFO] [mqtt_to_ros_bridge_node-3]: process started with pid [213708] [mqtt_to_ros_bridge_node-3] [INFO] [1674477353.721697169] [r0.mqtt_ros_bridge_node]: Connected with result code 0 [ros_to_mqtt_bridge_node-2] [INFO] [1674477353.739631580] [r0.ros_mqtt_bridge_node]: Connected with result code 0
Cheers,
Ben