-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
controller_server crashed with calling /lifecycle_manager/manage_nodes service #3762
Comments
Can you verify that it works in I believe we have handled this but it just hasn't been released to Humble binaries yet as a relatively recent fix. If that's the only issue, I can re-release Humble sooner to provide it. |
along with several more errors I can open a new issue for (maybe humble compatibility issue).
I removed the I couldn't test on |
But anyhow this is the answer:
That patch is actually already on humble, its just not in the released binaries. If you build humble from source, you're good to go! It will be released into binary format next time there is a release. I ran a release on August 4th and it looks like that release is happening today / tomorrow https://discourse.ros.org/t/preparing-for-humble-sync-2023-08-18/32950 so you should have humble binaries with this fix by the latest end of this week. |
https://discourse.ros.org/t/new-packages-for-humble-hawksbill-2023-08-18/32971 Update now and it should be patched |
Bug report
Steps to reproduce the issue
manage_nodes
service of the navigation lifecycle manager with a value of 3 -> Resetmanage_nodes
service of the navigation lifecycle manager with a value of 0 -> BringupExpected behavior
The Navigation stack should transition into the active state with no problem
Actual behavior
controller_server
crashes with the error:[controller_server-1] terminate called after throwing an instance of 'std::runtime_error' [controller_server-1] what(): Node '/local_costmap/local_costmap' has already been added to an executor.
and the node is dead and must be restarted.
The text was updated successfully, but these errors were encountered: