Skip to content
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

Error running gazebo_ros2_control_demo package: error: argument Call invalid choice: control #74

Closed
CSharpRon opened this issue May 9, 2021 · 1 comment · Fixed by #76

Comments

@CSharpRon
Copy link
Contributor

Expected Behavior

  • The container runs and the ros2 logs show that the cart was spawned successfully into the Gazebo process.

Actual Behavior

  • The ros2 logs show the loading of the publishers and controllers but then crashes with the following error message:

[INFO] [ros2-6]: process started with pid [127]
[ros2-6] usage: ros2 [-h] Call ros2 <command> -h for more detailed usage. ...
[ros2-6] ros2: error: argument Call ros2 <command> -h for more detailed usage.: invalid choice: 'control' (choose from 'action', 'bag', 'component', 'daemon', 'doctor', 'extension_points', 'extensions', 'interface', 'launch', 'lifecycle', 'multicast', 'node', 'param', 'pkg', 'run', 'security', 'service', 'topic', 'wtf')

Steps to Reproduce

  • git clone https://github.com/ros-simulation/gazebo_ros2_control
  • cd gazebo_ros2_control/Docker
  • docker build -t gazebo_ros2_control_demos:test .
  • docker run gazebo_ros2_control_demos:test

Observations

I believe this is due to the fact that there is no explicit dependency for ros2_control in the gazebo_ros2_control_demos/package.xml

The issue is fixed locally by adding this dependency and then rebuilding the container, as rosdep is then able to install ros-foxy-ros2-control

@ahcorde
Copy link
Collaborator

ahcorde commented May 10, 2021

@CSharpRon can you open a PR with the fix ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants