New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ros2 node list hangs when a node is on another machine on Windows and ROS_DOMAIN_ID is used #713
Comments
|
Can confirm I'm having this problem at least on some machines, but not all. Is there any fix/workaround/suggestions for further debugging that would be useful? All of my machines are using Robostack conda environments. The broken one is using
mamba_exact_broken_win11.yaml.txt The full package plan is attached. Machine Details
DDS is |
The working one is also The Linux machine with all the running nodes listed in the details below is an Ubuntu Focal machine also running Humble via Robostack.
Package list attached. mamba_exact_working_win11.yaml.txt Results
Machine Details
DDS is |
I confirm this issue in my MacBook Pro M2 machine. I am also using Robostack. Are there any updates regarding this issue? |
I know this ticket is for external-host scenario though, on the same single host scenario I just saw a similar issue. Easily reproducible with a Docker image (see "Steps to reproduce" section in moveit/moveit2_tutorials#713) then run |
Bug report
Required Info:
Steps to reproduce issue
On a linux laptop (not sure OS is important), set a ROS_DOMAIN_ID and start turtlesim_node
On a Windows machine using the Binary archive, try to list the node
Expected behavior
The windows machine would list the turtlesim node.
Actual behavior
The
ros2 node list
command hangs forever, and does not respond toCTRL + C
.Additional information
I'm using a Windows VM on Virtual Box on Ubuntu Focal with bridged networking (machine A). The other machine (machine B) is an Ubuntu Bionic running ROS 2 nightly in a Jammy Apptainer container. I'm able to ping the other machine from the windows VM.
Running a Jammy Apptainer container on A,
ros2 node list
works as expected. It's only the Windows machine that can't list the node.I could try a Humble workspace on machine B, but it's probably still similar enough.
ros2 node list
returns immediately on the Windows VM when noROS_DOMAIN_ID
is set.The text was updated successfully, but these errors were encountered: