You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Mikhail Gryzykhin (JIRA)" <ji...@apache.org> on 2018/07/27 21:16:00 UTC
[jira] [Commented] (BEAM-4686) Build Failure: gpg: keyserver
receive failed: unknown pubkey algorithm
[ https://issues.apache.org/jira/browse/BEAM-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16560340#comment-16560340 ]
Mikhail Gryzykhin commented on BEAM-4686:
-----------------------------------------
I've synced with Jason.
Seems that the easiest way would be to add retries.
I'll also check if there is any other source of keys available.
> Build Failure: gpg: keyserver receive failed: unknown pubkey algorithm
> ----------------------------------------------------------------------
>
> Key: BEAM-4686
> URL: https://issues.apache.org/jira/browse/BEAM-4686
> Project: Beam
> Issue Type: Bug
> Components: website
> Affects Versions: 2.6.0
> Reporter: Andrew Pilloud
> Assignee: Mikhail Gryzykhin
> Priority: Major
> Labels: flake
>
> I see this on a large percentage of builds:
>
> https://builds.apache.org/job/beam_PreCommit_Website_Stage/1145/console
> {code:java}
> [beam_PreCommit_Website_Stage] $ /bin/bash -xe /tmp/jenkins6730031359263725887.sh
> + gpg --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 7D2BAF1CF37B13E2069D6956105BD0E739499BDB
> gpg: requesting key D39DC0E3 from hkp server keys.gnupg.net
> gpg: requesting key 39499BDB from hkp server keys.gnupg.net
> gpgkeys: key 409B6B1796C275462A1703113804BB82D39DC0E3 can't be retrieved
> gpgkeys: key 7D2BAF1CF37B13E2069D6956105BD0E739499BDB can't be retrieved
> gpg: no valid OpenPGP data found.
> gpg: Total number processed: 0
> gpg: keyserver communications error: keyserver helper general error
> gpg: keyserver communications error: unknown pubkey algorithm
> gpg: keyserver receive failed: unknown pubkey algorithm
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)