Repository navigation
hotfix: pin MAVROS to 2.14.0 in the robot and GCS images (0.20.9) - #433
Open
JohnYanxinLiu wants to merge 4 commits into
Open
JohnYanxinLiu wants to merge 4 commits into
JohnYanxinLiu wants to merge 4 commits into
Conversation
…0.9) The robot and GCS images install MAVROS unpinned. MAVROS 2.15.0 creates its plugin nodes without the global remaps, so their topics and services move under .../mavros/mavros/*; the public Jazzy apt repository has carried that since the 2026-09-11 sync and now serves 2.16.0. The runtime stage of Dockerfile.robot and Dockerfile.gcs now add the ROS snapshot of 2026-06-18 and pin mavros, mavros-extras, mavros-msgs and libmavconn to 2.14.0-1* and mavlink to 2026.3.3-1* (priority 1001). The snapshot serves these versions for amd64 and arm64. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…stall lines Replace the apt preferences file with explicit version arguments on the existing install lines; keep the ROS snapshot source of 2026-06-18, now with a two-line comment. The release-notes entry is cut to one paragraph. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…MAVROS Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Collaborator
Author
|
/pytest |
JohnYanxinLiu
marked this pull request as ready for review
November 17, 2026 19:16
JohnYanxinLiu
marked this pull request as draft
November 17, 2026 19:21
JohnYanxinLiu
marked this pull request as ready for review
November 17, 2026 22:01
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Pins MAVROS to 2.14.0 in the robot and GCS images (VERSION → 0.20.9). Images built from
mainsince about 2026-09-11 get MAVROS 2.15+ and the stack's MAVROS topics and services are no longer where it looks for them.__node/__nsremap rules ... Plugin nodes are now created withuse_global_arguments(false), keeping their subnode name and the UAS namespace." Every plugin topic and service lands under.../mavros/mavros/<plugin>instead of.../mavros/<plugin>.Dockerfile.robotandDockerfile.gcsinstall MAVROS unpinned, so a rebuild takes whatever the public Jazzy repository serves.Dockerfile.robotandDockerfile.gcsadd the ROS snapshot of 2026-06-18 and installmavros(andmavros-extrason the robot),mavros-msgs,libmavconnandmavlinkat the versions from it. The ROS debs do not constrain each other's versions, so all of them are pinned; the snapshot has these for amd64 and arm64. Release notes get a dated 0.20.9 section. After merge the main → develop sync brings the pin intodevelop.Evidence
Topic check on this repository's own launch (
interface_bringup/launch/mavros_px4.launch.xmlunder/robot_1/interface,fcu_urlpointing at nothing), in a throwawayosrf/ros:jazzy-desktop-fullcontainer with MAVROS from apt vs from the snapshot:mavros/mavros/mavros/mavros/state/robot_1/interface/mavros/state/robot_1/interface/mavros/mavros/statesetpoint_raw/attitude.../mavros/setpoint_raw/attitude.../mavros/mavros/setpoint_raw/attitudelocal_position/odom.../mavros/local_position/odom.../mavros/mavros/local_position/odomset_mode,cmd/arming.../mavros/set_mode,.../mavros/cmd/arming.../mavros/mavros/set_mode,.../mavros/mavros/cmd/armingRead from source (not run):
mavros_interface,takeoff_landing_planner, the odometry input ininterface.launch.py,global_position/globalindds_router.yaml, the GCS Foxglove visualizer andaction_relay, and the system tests use the plain names.Testing
x86-64_dev) and GCS images from this branch locally. In both,dpkg -lshows the MAVROS packages at 2.14.0 andmavlinkat 2026.3.3./pytestrun on this PR stayed queued: noairstack-ephemeralrunner picked it up.pytest tests/ -m takeoff_hover_land --sim isaacsim --num-robots 1: 4 passed (test_px4_ready,test_takeoff,test_hover,test_landing) in 190 s.pytest tests/ -m build_packages --num-robots 1: 3 passed, 1 failed. The failure istest_colcon_build_ms_airsim, because its image was not built.tests/requirements.txtinstalls today, stops at collection intests/harness/collection.py:168before any test runs. That is also why the "Python unit and harness contracts" check fails on this PR.Follow-up
Support 2.15 and later by fixing the remaps for the plugin nodes, then remove the pin and the snapshot source.
🤖 Generated with Claude Code