ros-tooling/setup-ros

Update ROS2 GPG key

Closed this issue · 7 comments

niosus commented

Description

As the ROS2 GPG key has recently expired, the current version of this action fails with an error:

  W: GPG error: http://packages.ros.org/ros/ubuntu focal InRelease: The following signatures were invalid: EXPKEYSIG F42ED6FBAB17C654 Open Robotics <info@osrfoundation.org>
  E: The repository 'http://packages.ros.org/ros/ubuntu focal InRelease' is not signed.
  W: GPG error: http://packages.ros.org/ros2/ubuntu focal InRelease: The following signatures were invalid: EXPKEYSIG F42ED6FBAB17C654 Open Robotics <info@osrfoundation.org>
  E: The repository 'http://packages.ros.org/ros2/ubuntu focal InRelease' is not signed.

Expected Behavior

The action should complete without issues.

To Reproduce

I believe every build with this action will fail for now.

The setup we are running 
  name: ROS 2 CI Action new release
  
  on:
  pull_request:
  push:
    branches:
      - master
      
  jobs:
  build-and-test:
    runs-on: ubuntu-latest
    steps:
    - name: Setup ROS 2
      uses: ros-tooling/setup-ros@0.2.1
      with:
        required-ros-distributions: foxy

    - name: Run Tests
      uses: ros-tooling/action-ros-ci@0.2.1
      with:
        package-name: umrr_ros2_driver
        import-token: ${{ secrets.REPO_TOKEN }}
        target-ros2-distro: foxy
niosus commented

I also see the comment here: #405 (comment) that says this should already be taken care of, so I might be doing smth wrong on my side. I'm happy to provide more details if needed.

christophebedard commented

Can you provide a link to a failing CI job?

niosus commented

Unfortunately not as it is a private project 😞

christophebedard commented

Or maybe some copy pasted logs with private stuff removed? It's hard to say without a concrete instance where it failed. Our tests cover this and other users are reporting that it works fine 😕

niosus commented

@christophebedard weird. I created a new repo and there it seems to work 🤔 I will close this for now and will reopen if there is any additional details. Sorry for the noise.

christophebedard commented

Weird. It's still an issue if it doesn't work on one repo 😆

niosus commented

@christophebedard ok, I got it working and to be honest I have no idea why it did not before. Anyway, this is probably on me. Again, sorry for the noise and thanks for the quick response! 🙏

  • 👍1