-
Notifications
You must be signed in to change notification settings - Fork 47
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
Foxy | Regression: Default RMW no longer ships with DDS security features #252
Comments
@JaimeMartin did you folks change your default config by any chance? |
This looks like probably a packaging bug. If I look at https://build.ros2.org/view/Fbin_uF64/job/Fbin_uF64__fastrtps__ubuntu_focal_amd64__binary/9/consoleFull (the fastrtps build back in May), I see this:
If I look at the latest build at https://build.ros2.org/view/Fbin_uF64/job/Fbin_uF64__fastrtps__ubuntu_focal_amd64__binary/24/consoleFull , I see this:
Notice that |
It looks like a bad rebase from the last release: ros2-gbp/fastrtps-release@0ed7d05 removed the template that had |
Thanks for the quick triage @clalancette! |
It looks like Dashing probably has the same problem (https://build.ros2.org/view/Dbin_uB64/job/Dbin_uB64__fastrtps__ubuntu_bionic_amd64__binary/19/consoleFull), though Rolling is fine. |
The |
This issue has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/preparing-for-foxy-sync-2021-03-01/19178/1 |
All right, this has been fixed in the testing repositories for both Foxy and Dashing. A sync is scheduled for Foxy. I'm going to close this issue out, thanks for reporting @ruffsl . |
@clalancette , do we know yet how this regression slipped under the radar of existing tests and made it's way into a released public sync? Did the system security tests in CI silently fail? What should we do now to prevent this again? |
Debian packages don't get tested that's why the regression was not caught. Not sure how the regression actually happened, as far as I recall patches always got reapplied on rebase when making a new release. @nuclearsandwich @clalancette do you know what happened there and how to prevent it from happening in the future ? As a side note: |
It's a combination of 3 things:
Improving any of those would help prevent this from happening again. Unfortunately, none of them are easy to do. |
This issue has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/new-packages-for-foxy-fitzroy-2021-03-01/19224/1 |
This issue has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/preparing-for-dashing-sync-2021-03-04/19233/1 |
Hi, I recently installed foxy on ubuntu 20.04 from binaries. I still have this problem. How do i get the updated packages for fastrtps? |
You may want to check what package version you have installed with apt. This is what is in the repo as of writing:
|
Hi, I just checked it again. It's working now, seems the problem is with my security keys. |
I also met this issue, the command I use as following: |
Bug report
Not sure if this is the best place to report this, but I think the default rmw for Foxy was re-released without DDS security enabled?
Required Info:
ros-foxy-sros2/focal,now 0.9.4-1focal.20210125.232905 amd64 [installed,automatic]
ros-foxy-fastrtps/focal,now 2.0.2-1focal.20201210.051121 amd64 [installed,automatic]
Steps to reproduce issue
Follow the demo documented here:
https://github.com/ros2/sros2/blob/foxy/SROS2_Linux.md
Expected behavior
Security works and demo nodes connect and exchange messages via Secure DDS.
Actual behavior
Additional information
Discovered while update sros2 demos for latest
ros:foxy
images:ros-swg/turtlebot3_demo#34 (comment)
The text was updated successfully, but these errors were encountered: