`ros2 node list -a` reports an extra node the first time it is run.

Required Info:

• Operating System:
  • Ubuntu Focal
• Installation type:
  • source
• Version or commit hash:
  • master
• DDS implementation:
  • rmw_cyclonedds_cpp, rmw_fastrtps_cpp
• Client library (if applicable):
  • N/A

Steps to reproduce issue

echo on
ros2 daemon stop; ros2 node list -a
ros2 node list --no-daemon; ros2 node list -a
ros2 daemon start; ros2 node list -a

Expected behavior

All invocations of ros2 node list show the same nodes.

The daemon has been stopped
/_ros2cli_daemon_0

/_ros2cli_daemon_0

The daemon is already running
/_ros2cli_daemon_0

Actual behavior

The daemon has been stopped
/_ros2cli_293393
/_ros2cli_daemon_0

/_ros2cli_daemon_0

The daemon is already running
/_ros2cli_daemon_0

If the daemon is stopped when you run ros2 node list -a, an additional node is shown, presumably one that is spun up to start the daemon. This node does not show up without the -a flag, nor with the --no-daemon flag.

Additional information

This may be related to CI failure of test_list_all_node_count at http://build.ros2.org/view/Fci/job/Fci__nightly-cyclonedds_ubuntu_focal_amd64/53/testReport/ros2node.test/test_cli/test_cli/

This is probably unrelated to any current CI test failures