Skip to content

Commit 26e61f4

Browse files
committed
fix(demos/ota): launch fault_manager_node so /faults endpoint responds
Without /fault_manager/* services running, the gateway's /faults endpoint hangs waiting for the service call (default 5s timeout) and the Faults Dashboard panel surfaces it as 503. Adds 'ros2 run ros2_medkit_fault_manager fault_manager_node' to entrypoint.sh - the gateway image already builds the package; we just need to run it. Defaults are fine for the demo (SQLite at /var/lib/ros2_medkit/faults.db, snapshot capture enabled).
1 parent 43a66e3 commit 26e61f4

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

demos/ota_nav2_sensor_fix/entrypoint.sh

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,12 @@ source /ws/install/setup.bash
1515
# Demo nodes the plugin will swap (broken_lidar -> fixed_lidar) and
1616
# uninstall (broken_lidar_legacy). obstacle_classifier_v2 is installed
1717
# fresh by the demo and not started here.
18+
# Fault manager: serves /fault_manager/* services that the gateway's
19+
# /faults endpoint calls. Without it /faults hangs because the gateway
20+
# blocks waiting for the service. Default parameters are fine for the
21+
# demo (in-memory store, no persistence).
22+
ros2 run ros2_medkit_fault_manager fault_manager_node &
23+
1824
ros2 run broken_lidar broken_lidar_node &
1925
ros2 run broken_lidar_legacy broken_lidar_legacy &
2026

0 commit comments

Comments
 (0)