Skip to content
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

Sync gpgme error: Unusable secret key #902

Open
tfoote opened this issue Aug 19, 2021 · 7 comments
Open

Sync gpgme error: Unusable secret key #902

tfoote opened this issue Aug 19, 2021 · 7 comments
Assignees

Comments

@tfoote
Copy link
Member

tfoote commented Aug 19, 2021

I'm refiling osrf/infrastructure#3 (comment) here so that we can track this.

A somewhat similar thing happened to Melodic over the weekend; see https://discourse.ros.org/t/testing-repository-empty-amd64/20908 for some more of the details.

I'm wondering if it would make sense to have the sync-to-testing jobs run nightly, as a backup in case something failed. That way the time frame of the breakage (if it does occur) would at least be time-limited.

In the failed melodic log noticed that there's actually a real error that we should not be having

13:57:15 gpgme gave error GPGME:54:  Unusable secret key

We should make sure that doesn't happen.

@tfoote
Copy link
Member Author

tfoote commented Sep 21, 2021

There was just another instance of this today:

https://build.ros2.org/job/Grel_sync-packages-to-testing_focal_arm64/104/consoleFull

23:29:18 removing 'ros-galactic-urg-node' from 'focal|main|source'..gpgme gave error GPGME:54:  Unusable secret key
23:29:24 ERROR: Could not finish exporting 'focal'!

@clalancette
Copy link
Contributor

clalancette commented Sep 22, 2021

There was another instance of this on Melodic as well: https://build.ros.org/job/Mrel_sync-packages-to-testing_bionic_amd64/726/console

23:28:38 removing 'ros-melodic-yosemite-valley' from gpgme gave error GPGME:54:  Unusable secret key
23:28:38 ERROR: Could not finish exporting 'bionic'!

@tfoote
Copy link
Member Author

tfoote commented Sep 22, 2021

These last jobs failed within a minute of each other on separate days. Do we have a server maintenance task managing the gpg keys at that time? The earlier case is also just before the hour too.

@nuclearsandwich nuclearsandwich self-assigned this Dec 8, 2021
@nuclearsandwich
Copy link
Contributor

I saw a similar but different GPG error importing the jammy repositories today. https://build.ros2.org/job/import_upstream/357/

I am going to block out some time for this toward the start of next year.

@ijnek
Copy link
Member

ijnek commented May 10, 2022

This error suddenly came up in one of my packages today: https://build.ros2.org/job/Hrel_import-package/4137/consoleFull

This is the job that triggered the Hrel_import_package: https://build.ros2.org/job/Hbin_ujv8_uJv8__rqt_image_overlay_layer__ubuntu_jammy_arm64__binary/4/consoleFull


Update

The build passed in the next build "Started by user SYSTEM": https://build.ros2.org/job/Hbin_ujv8_uJv8__rqt_image_overlay_layer__ubuntu_jammy_arm64__binary/5/ without any changes.

@ijnek
Copy link
Member

ijnek commented Jul 12, 2022

@tfoote
Copy link
Member Author

tfoote commented Jun 2, 2023

We had another instance of this for noetic sync to testing: https://build.ros.org/view/Nbin_uF64/job/Nrel_sync-packages-to-testing_focal_amd64/1134/console

It's likely still happening in the background for individual package syncs but they retry sooner so as not to be noticed.

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

No branches or pull requests

4 participants