Actually, among the hundreds of failed messages, the "No public key" issues still occurred several times:
failureMessage No public key: Key with id: (b3fa653d57300d45) was not able to be located on http://gpg-keyserver.de/. Upload your public key and try the operation again. failureMessage No public key: Key with id: (b3fa653d57300d45) was not able to be located on http://pool.sks-keyservers.net:11371. Upload your public key and try the operation again. failureMessage No public key: Key with id: (b3fa653d57300d45) was not able to be located on http://pgp.mit.edu:11371. Upload your public key and try the operation again. Once the close operation returned, I will upload sample files which may help troubleshoot the issue. Thanks, On Sat, Jan 12, 2019 at 9:04 PM Wangda Tan <wheele...@gmail.com> wrote: > Thanks David for the quick response! > > I just retried, now the "No public key" issue is gone. However, the > issue: > > failureMessage Failed to validate the pgp signature of > '/org/apache/hadoop/hadoop-mapreduce-client-jobclient/3.1.2/hadoop-mapreduce-client-jobclient-3.1.2-tests.jar', > check the logs. > failureMessage Failed to validate the pgp signature of > '/org/apache/hadoop/hadoop-mapreduce-client-jobclient/3.1.2/hadoop-mapreduce-client-jobclient-3.1.2-test-sources.jar', > check the logs. > failureMessage Failed to validate the pgp signature of > '/org/apache/hadoop/hadoop-mapreduce-client-jobclient/3.1.2/hadoop-mapreduce-client-jobclient-3.1.2.pom', > check the logs. > > > Still exists and repeated hundreds of times. Do you know how to access the > logs mentioned by above log? > > Best, > Wangda > > On Sat, Jan 12, 2019 at 8:37 PM David Nalley <da...@gnsa.us> wrote: > >> On Sat, Jan 12, 2019 at 9:09 PM Wangda Tan <wheele...@gmail.com> wrote: >> > >> > Hi Devs, >> > >> > I'm currently rolling Hadoop 3.1.2 release candidate, however, I saw an >> issue when I try to close repo in Nexus. >> > >> > Logs of https://repository.apache.org/#stagingRepositories >> (orgapachehadoop-1183) shows hundreds of lines of the following error: >> > >> > failureMessage No public key: Key with id: (b3fa653d57300d45) was not >> able to be located on http://gpg-keyserver.de/. Upload your public key >> and try the operation again. >> > failureMessage No public key: Key with id: (b3fa653d57300d45) was not >> able to be located on http://pool.sks-keyservers.net:11371. Upload your >> public key and try the operation again. >> > failureMessage No public key: Key with id: (b3fa653d57300d45) was not >> able to be located on http://pgp.mit.edu:11371. Upload your public key >> and try the operation again. >> > ... >> > failureMessage Failed to validate the pgp signature of >> '/org/apache/hadoop/hadoop-yarn-registry/3.1.2/hadoop-yarn-registry-3.1.2-tests.jar', >> check the logs. >> > failureMessage Failed to validate the pgp signature of >> '/org/apache/hadoop/hadoop-yarn-registry/3.1.2/hadoop-yarn-registry-3.1.2-test-sources.jar', >> check the logs. >> > failureMessage Failed to validate the pgp signature of >> '/org/apache/hadoop/hadoop-yarn-registry/3.1.2/hadoop-yarn-registry-3.1.2-sources.jar', >> check the logs. >> > >> > >> > This is the same key I used before (and finished two releases), the >> same environment I used before. >> > >> > I have tried more than 10 times in the last two days, no luck. And >> closing the repo takes almost one hour (Regular time is less than 1 min) >> and always fail at the last. >> > >> > I used following commands to validate key exists on key servers >> > >> > gpg --keyserver pgp.mit.edu --recv-keys 57300D45 >> > gpg: WARNING: unsafe permissions on homedir '/Users/wtan/.gnupg' >> > gpg: key B3FA653D57300D45: 1 signature not checked due to a missing key >> > gpg: key B3FA653D57300D45: "Wangda tan <wan...@apache.org>" not changed >> > gpg: Total number processed: 1 >> > gpg: unchanged: 1 >> > >> > gpg --keyserver pool.sks-keyservers.net --recv-keys B3FA653D57300D45 >> > gpg: WARNING: unsafe permissions on homedir '/Users/wtan/.gnupg' >> > gpg: key B3FA653D57300D45: 1 signature not checked due to a missing key >> > gpg: key B3FA653D57300D45: "Wangda tan <wan...@apache.org>" not changed >> > gpg: Total number processed: 1 >> > gpg: unchanged: 1 >> > >> >> Both of these report that your key was not found. >> I took the key from the KEYS file and uploaded it to both of those >> servers. >> >> You might try the release again and see if this resolves the issue. >> >
