Skip to content

Joint trajectory controller fails to spawn for ROS 2 Lyrical on Ubuntu 26.04 #407

Closed

Description

@mhubii

Following error:

[ros2_control_node-2] [INFO] [1789490699.320928135] [lbr.controller_manager]: Loading controller : 'joint_trajectory_controller' of type 'joint_trajectory_controller/JointTrajectoryController'
[ros2_control_node-2] [INFO] [1789490699.320978587] [lbr.controller_manager]: Loading controller 'joint_trajectory_controller'
[ros2_control_node-2] Exception thrown during init stage with message: Invalid value set during initialization for parameter 'joints': Length of parameter 'joints' is '0' but must be greater than '0' 
[ros2_control_node-2] [ERROR] [1789490699.331049657] [lbr.joint_trajectory_controller]: Calling shutdown transition of controller node 'joint_trajectory_controller' due to init failure.
[ros2_control_node-2] [ERROR] [1789490699.331124185] [lbr.controller_manager]: Could not initialize the controller named 'joint_trajectory_controller'
[spawner-3] [FATAL] [1789490699.335769528] [lbr.spawner_joint_state_broadcaster]: Failed loading controller joint_trajectory_controller

Can be fixed by providing the spawner node a --param-file. Introduced upstream in ros-controls/ros2_control#1502 with demos added in ros-controls/ros2_control_demos#502.

Here to be added to launch arguments for gazebo / hardware / mock + dual arm demo:

Activity

  1. added theissue type on Sep 15, 2026
  2. changed the issue type fromtoon Sep 16, 2026
  3. linked a pull request that will close this issuedecouple parameters (#407) #411on Sep 16, 2026
  4. added a commit that references this issue on Sep 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions