Open norro opened 5 years ago
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.
When calling
ros2 lifecycle set
, the tool will abort with an error ("Node not found"). Reproduce: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