Exception when instantiating ActionServer as part of ROS package tests

[sea-bass]

Bug report

Required Info:

• Operating System:
  • Ubuntu 22.04
• Installation type:
  • Binaries
• Version or commit hash:
  • Latest binaries of Humble/Iron/Rolling
• DDS implementation:
  • Fast DDS or Cyclone DDS (doesn't make a difference)
• Client library (if applicable):
  • rclpy

Steps to reproduce issue

I have a test that is failing as part of this PR (RobotWebTools/rosbridge_suite#886) when I try to instantiate an action server, noting that:

• This only happens on Iron and Rolling, but not on Humble
• This only happens when I run using colcon test (which in turn uses ament_add_pytest_test CMake capability), but not if I run it directly using Python

Can't seem to figure out why this would be the case, so figured I'd elevate it here? Thank you!

The code:

from example_interfaces.action import Fibonacci

class MyClass:
    def __init__(self, node):
        self.action_server = ActionServer(
            node,  # Just an rclpy.Node
            Fibonacci,
            "/fibonacci_action_1",
            self.execute_callback,
        )

The error:

          self.action_server = ActionServer(
      /opt/ros/rolling/lib/python3.10/site-packages/rclpy/action/server.py:264: in __init__
          self._logger = self._node.get_logger().get_child('action_server')
      _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
      
      self = <rclpy.impl.rcutils_logger.RcutilsLogger object at 0x7f730bfe9270>
      name = 'action_server'
      
          def get_child(self, name):
              if not name:
                  raise ValueError('Child logger name must not be empty.')
          
              if self.name:
                  # Prepend the name of this logger
      >           _rclpy.rclpy_logging_rosout_add_sublogger(self.name, name)
      E           RuntimeError: Failed to call rcl_logging_rosout_add_sublogger

Expected behavior

Should not raise an exception.

Actual behavior

Raises an exception.

[sea-bass]

Seems the issue originates from #982, whereas the exception comes from #1084

[fujitatomoya]

@iuhilnehc-ynos can you take a look at this?