Skip to content

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
mainfrom
hotfix/pin-mavros-2-14
Open

JohnYanxinLiu wants to merge 4 commits into
mainfrom
hotfix/pin-mavros-2-14

Conversation

@JohnYanxinLiu

@JohnYanxinLiu JohnYanxinLiu commented Nov 16, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Pins MAVROS to 2.14.0 in the robot and GCS images (VERSION → 0.20.9). Images built from main since about 2026-09-11 get MAVROS 2.15+ and the stack's MAVROS topics and services are no longer where it looks for them.

  • Cause. MAVROS 2.15.0 (tagged 2026-08-08) changed plugin-node creation. From its CHANGELOG: "Dynamically created plugin nodes no longer inherit process-global __node/__ns remap rules ... Plugin nodes are now created with use_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.robot and Dockerfile.gcs install MAVROS unpinned, so a rebuild takes whatever the public Jazzy repository serves.
  • When. From the ROS snapshot indexes: 2026-06-18 has 2.14.0, 2026-09-11 has 2.15.1 (the first public Jazzy build with the change), 2026-10-05 has 2.16.0 (what apt serves now). Images built before about 2026-09-11 keep 2.14.
  • Fix. The runtime stage of Dockerfile.robot and Dockerfile.gcs add the ROS snapshot of 2026-06-18 and install mavros (and mavros-extras on the robot), mavros-msgs, libmavconn and mavlink at 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 into develop.

Evidence

Topic check on this repository's own launch (interface_bringup/launch/mavros_px4.launch.xml under /robot_1/interface, fcu_url pointing at nothing), in a throwaway osrf/ros:jazzy-desktop-full container with MAVROS from apt vs from the snapshot:

2.14.0 (this PR) 2.16.0 (apt today)
MAVROS topics 153, none under mavros/mavros/ 155, all under mavros/mavros/
state /robot_1/interface/mavros/state /robot_1/interface/mavros/mavros/state
setpoint_raw/attitude .../mavros/setpoint_raw/attitude .../mavros/mavros/setpoint_raw/attitude
local_position/odom .../mavros/local_position/odom .../mavros/mavros/local_position/odom
service set_mode, cmd/arming .../mavros/set_mode, .../mavros/cmd/arming .../mavros/mavros/set_mode, .../mavros/mavros/cmd/arming

Read from source (not run): mavros_interface, takeoff_landing_planner, the odometry input in interface.launch.py, global_position/global in dds_router.yaml, the GCS Foxglove visualizer and action_relay, and the system tests use the plain names.

Testing

  • Built the robot (x86-64_dev) and GCS images from this branch locally. In both, dpkg -l shows the MAVROS packages at 2.14.0 and mavlink at 2026.3.3.
  • Ran this repository's system tests locally against those images, with the Isaac Sim image pulled from the registry cache as CI does. The /pytest run on this PR stayed queued: no airstack-ephemeral runner 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 is test_colcon_build_ms_airsim, because its image was not built.
  • The tests ran with pytest 9.1.1. pytest 9.2.0, which tests/requirements.txt installs today, stops at collection in tests/harness/collection.py:168 before 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

JohnYanxinLiu and others added 4 commits November 16, 2026 15:54
…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>
@JohnYanxinLiu

Copy link
Copy Markdown
Collaborator Author

/pytest

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant