-
Bug
-
Resolution: Unresolved
-
Medium
In puppet-opendaylight tests, as they install RVM and the PGP key used to sign it, there are intermittent errors like this:
+ gpg2 --keyserver hkp://pool.sks-keyservers.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 gpg: directory `/home/jenkins/.gnupg' created gpg: new configuration file `/home/jenkins/.gnupg/gpg.conf' created gpg: WARNING: options in `/home/jenkins/.gnupg/gpg.conf' are not yet active during this run gpg: keyring `/home/jenkins/.gnupg/secring.gpg' created gpg: keyring `/home/jenkins/.gnupg/pubring.gpg' created gpg: requesting key D39DC0E3 from hkp server pool.sks-keyservers.net gpgkeys: key 409B6B1796C275462A1703113804BB82D39DC0E3 can't be retrieved gpg: no valid OpenPGP data found. gpg: Total number processed: 0 Build step 'Execute shell' marked build as failure
Most of the time that step passes with:
+ gpg2 --keyserver hkp://pool.sks-keyservers.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 gpg: directory `/home/jenkins/.gnupg' created gpg: new configuration file `/home/jenkins/.gnupg/gpg.conf' created gpg: WARNING: options in `/home/jenkins/.gnupg/gpg.conf' are not yet active during this run gpg: keyring `/home/jenkins/.gnupg/secring.gpg' created gpg: keyring `/home/jenkins/.gnupg/pubring.gpg' created gpg: requesting key D39DC0E3 from hkp server pool.sks-keyservers.net gpg: /home/jenkins/.gnupg/trustdb.gpg: trustdb created gpg: key D39DC0E3: public key "Michal Papis (RVM signing) <mpapis@gmail.com>" imported gpg: no ultimately trusted keys found gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1)