{"action":"closed","issue":{"url":"https://api.github.com/repos/kryptco/kr/issues/154","repository_url":"https://api.github.com/repos/kryptco/kr","labels_url":"https://api.github.com/repos/kryptco/kr/issues/154/labels{/name}","comments_url":"https://api.github.com/repos/kryptco/kr/issues/154/comments","events_url":"https://api.github.com/repos/kryptco/kr/issues/154/events","html_url":"https://github.com/kryptco/kr/issues/154","id":264701412,"node_id":"MDU6SXNzdWUyNjQ3MDE0MTI=","number":154,"title":"Host PGP public key on our own infrastructure","user":{"login":"gae123","id":6157123,"node_id":"MDQ6VXNlcjYxNTcxMjM=","avatar_url":"https://avatars3.githubusercontent.com/u/6157123?v=4","gravatar_id":"","url":"https://api.github.com/users/gae123","html_url":"https://github.com/gae123","followers_url":"https://api.github.com/users/gae123/followers","following_url":"https://api.github.com/users/gae123/following{/other_user}","gists_url":"https://api.github.com/users/gae123/gists{/gist_id}","starred_url":"https://api.github.com/users/gae123/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gae123/subscriptions","organizations_url":"https://api.github.com/users/gae123/orgs","repos_url":"https://api.github.com/users/gae123/repos","events_url":"https://api.github.com/users/gae123/events{/privacy}","received_events_url":"https://api.github.com/users/gae123/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-10-11T19:09:09Z","updated_at":"2018-06-13T15:22:07Z","closed_at":"2018-06-13T15:22:07Z","author_association":"NONE","body":"I have some automated infrastructure that builds docker images that install kr among other things. It is triggered automatically by other changes and had been very reliable until I added the kr installation step. It is an amazon linux and  the steps are exactly what you document here: https://krypt.co/install/\r\n\r\nHere is a history of failures the past few days, timestamps are PDT. The failures are transient, ie not reproducible every time, but the frequency is alarming.\r\n\r\n**Oct 9 2017**\r\n\r\n```\r\n04:00:15 Step 13/55 : RUN gpg --keyserver=hkp://pgp.mit.edu:80 --recv-keys \"C4A05888A1C4FA02E1566F859F2A29A569653940\"\r\n04:00:15  ---> Running in c42b006adc89\r\n04:00:15 \u001B[91mgpg: directory `/root/.gnupg' created\r\n04:00:15 \u001B[0m\u001B[91mgpg: new configuration file `/root/.gnupg/gpg.conf' created\r\n04:00:15 gpg: WARNING: options in `/root/.gnupg/gpg.conf' are not yet active during this run\r\n04:00:15 gpg: keyring `/root/.gnupg/secring.gpg' created\r\n04:00:15 \u001B[0m\u001B[91mgpg: keyring `/root/.gnupg/pubring.gpg' created\r\n04:00:15 \u001B[0m\u001B[91mgpg: requesting key 69653940 from hkp server pgp.mit.edu\r\n04:00:15 \u001B[0mgpgkeys: key C4A05888A1C4FA02E1566F859F2A29A569653940 can't be retrieved\r\n04:00:29 \u001B[91mgpg: no valid OpenPGP data found.\r\n04:00:29 gpg: Total number processed: 0\r\n04:00:29 gpg: keyserver communications error: keyserver helper general error\r\n04:00:29 gpg: keyserver communications error: Invalid public key algorithm\r\n04:00:29 gpg: keyserver receive failed: Invalid public key algorithm\r\n04:00:29 \u001B[0mThe command '/bin/sh -c gpg --keyserver=hkp://pgp.mit.edu:80 --recv-keys \"C4A05888A1C4FA02E1566F859F2A29A569653940\"' returned a non-zero code: 2\r\n04:00:29 Build step 'Execute shell' marked build as failure\r\n04:00:29 [htmlpublisher] Archiving HTML reports...\r\n04:00:29 Email was triggered for: Failure\r\n04:00:33 Finished: FAILURE\r\n```\r\n\r\n**Oct 11 2017**\r\n```\r\n10:03:18 Step 13/55 : RUN gpg --keyserver=hkp://pgp.mit.edu:80 --recv-keys \"C4A05888A1C4FA02E1566F859F2A29A569653940\"\r\n10:03:18  ---> Running in e362374477ad\r\n10:03:18 \u001B[91mgpg: directory `/root/.gnupg' created\r\n10:03:18 \u001B[0m\u001B[91mgpg: new configuration file `/root/.gnupg/gpg.conf' created\r\n10:03:18 gpg: WARNING: options in `/root/.gnupg/gpg.conf' are not yet active during this run\r\n10:03:18 gpg: keyring `/root/.gnupg/secring.gpg' created\r\n10:03:18 gpg: keyring `/root/.gnupg/pubring.gpg' created\r\n10:03:18 \u001B[0m\u001B[91mgpg: requesting key 69653940 from hkp server pgp.mit.edu\r\n10:03:18 \u001B[0m\u001B[91mgpg: keyserver timed out\r\n10:05:18 gpg: keyserver receive failed: Keyserver error\r\n10:05:18 \u001B[0mThe command '/bin/sh -c gpg --keyserver=hkp://pgp.mit.edu:80 --recv-keys \"C4A05888A1C4FA02E1566F859F2A29A569653940\"' returned a non-zero code: 2\r\n10:05:18 Build step 'Execute shell' marked build as failure\r\n10:05:18 [htmlpublisher] Archiving HTML reports...\r\n10:05:18 Email was triggered for: Failure\r\n10:05:22 Finished: FAILURE\r\n```\r\n\r\n```\r\n11:08:57 Step 13/55 : RUN gpg --keyserver=hkp://pgp.mit.edu:80 --recv-keys \"C4A05888A1C4FA02E1566F859F2A29A569653940\"\r\n11:08:57  ---> Running in 329b392b2bcb\r\n11:08:57 \u001B[91mgpg: directory `/root/.gnupg' created\r\n11:08:57 \u001B[0m\u001B[91mgpg: new configuration file `/root/.gnupg/gpg.conf' created\r\n11:08:57 gpg: WARNING: options in `/root/.gnupg/gpg.conf' are not yet active during this run\r\n11:08:57 gpg: keyring `/root/.gnupg/secring.gpg' created\r\n11:08:57 gpg: keyring `/root/.gnupg/pubring.gpg' created\r\n11:08:57 \u001B[0m\u001B[91mgpg: requesting key 69653940 from hkp server pgp.mit.edu\r\n11:08:57 \u001B[0m\u001B[91mgpg: keyserver timed out\r\n11:10:57 gpg: keyserver receive failed: Keyserver error\r\n11:10:57 \u001B[0mThe command '/bin/sh -c gpg --keyserver=hkp://pgp.mit.edu:80 --recv-keys \"C4A05888A1C4FA02E1566F859F2A29A569653940\"' returned a non-zero code: 2\r\n11:10:57 Build step 'Execute shell' marked build as failure\r\n11:10:58 [htmlpublisher] Archiving HTML reports...\r\n11:10:58 Email was triggered for: Failure\r\n11:11:01 Finished: FAILURE\r\n```"}}
{"actor":{"display_login":"kcking"}}