It’s potentially worth noting that since Humble / 22.04 Rolling moved to Fast-DDS, we have seen an uptick in issues relating to communication failures.
- lifecycle manager wait for service should have a finite, or at least configurable, timeout. · Issue #3033 · ros-planning/navigation2 · GitHub
- Costmap Topic Collision Checker not working in Humble/Rolling · Issue #3014 · ros-planning/navigation2 · GitHub
- Nav2 lifecycle manager won't startup nodes · Issue #2917 · ros-planning/navigation2 · GitHub
- FastDDS without Discovery Server?
If switching DDS providers, it solves them. I’d like to work with eProsima to get these resolved so that we can support Nav2 users in Fast-DDS as well, but there are some hiccups to be worked through.