system_modes icon indicating copy to clipboard operation
system_modes copied to clipboard

(sub-)systems not recognized by ros2 lifecycle cli

Open norro opened this issue 6 years ago • 1 comments

When calling ros2 lifecycle set, the tool will abort with an error ("Node not found"). Reproduce:

  1. Start mode manager with example system (see system_modes_examples
  2. Execute ros2 lifecycle set actuation configure

Expected result: actuation system is set to inactive

Actual result: rros2 lifecycle returns "Node not found", actuation system remains unchanged

norro avatar Dec 12 '18 16:12 norro

Not sure any more, if this is really an issue (as in: error). The reason for this behavior is that ros2 lifecycle is querying the nodegraph before performing the call. The nodegraph correctly returns "Node not found". So this is actually intended behavior.

I will still keep this issue open, as it would still be nice if it would be completely transparent, if I am calling a node or subsystem.

norro avatar Feb 17 '20 15:02 norro