The HTTP REST API fans out fault queries to aggregation peers (AggregationManager::fan_out_get), but the ROS 2 SOVD service interface returns only the local fault manager's faults.
In a federated setup (a gateway with aggregation.enabled and peer gateways), /<prefix>/list_entity_faults and the list_all_faults plugin path return only locally-managed faults. A ROS 2 client therefore cannot see faults that originate on peers, even though the HTTP /api/v1/faults and /api/v1/<entity>/faults endpoints already expose them via fan-out.
The ROS 2 service interface and the HTTP API should be consistent: both should surface aggregated peer faults.
The HTTP REST API fans out fault queries to aggregation peers (
AggregationManager::fan_out_get), but the ROS 2 SOVD service interface returns only the local fault manager's faults.In a federated setup (a gateway with
aggregation.enabledand peer gateways),/<prefix>/list_entity_faultsand thelist_all_faultsplugin path return only locally-managed faults. A ROS 2 client therefore cannot see faults that originate on peers, even though the HTTP/api/v1/faultsand/api/v1/<entity>/faultsendpoints already expose them via fan-out.The ROS 2 service interface and the HTTP API should be consistent: both should surface aggregated peer faults.