Closed slowtokyo closed 6 years ago
slowtokyo
commented
6 years ago This seems to have been a temporary issue and did not happen on a subsequent install so I can't replicate it. Feel free to close. However I'll leave it open for now in case someone wants to investigate.
dguido
commented
6 years ago Thanks!
TC1977
commented
6 years ago Just ran into the same error while trying to test out the ansible2.5 branch on an AWS EC2 instance using the local install option. Here's the output from ./algo -vvv:
TASK [dns_encryption : Add the repository] *************************************
task path: /home/ubuntu/algo/roles/dns_encryption/tasks/ubuntu.yml:2
fatal: [localhost]: FAILED! => {
"changed": false,
"cmd": "apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 EEE1EE950DF627C6879627B56C46343FA0B41DB7",
"invocation": {
"module_args": {
"codename": "artful",
"filename": null,
"install_python_apt": true,
"mode": null,
"repo": "ppa:shevchuk/dnscrypt-proxy",
"state": "present",
"update_cache": true,
"validate_certs": true
}
},
"msg": "Warning: apt-key output should not be parsed (stdout is not a terminal)\ngpg: keyserver receive failed: No data",
"rc": 2,
"stderr": "Warning: apt-key output should not be parsed (stdout is not a terminal)\ngpg: keyserver receive failed: No data\n",
"stderr_lines": [
"Warning: apt-key output should not be parsed (stdout is not a terminal)",
"gpg: keyserver receive failed: No data"
],
"stdout": "Executing: /tmp/apt-key-gpghome.smruv9dzG8/gpg.1.sh --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 EEE1EE950DF627C6879627B56C46343FA0B41DB7\n",
"stdout_lines": [
"Executing: /tmp/apt-key-gpghome.smruv9dzG8/gpg.1.sh --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 EEE1EE950DF627C6879627B56C46343FA0B41DB7"
]
}I'll start over and see if I can replicate.
TC1977
commented
6 years ago Couldn't replicate it, even doing a local install of the ansible2.5 branch on the same EC2 instance.
bmoquist
commented
6 years ago I experienced a similar issue today using the current distribution to deploy to AWS EC2 -- the error at a different part of the process during Wireguard repository configuration. I made a second attempt starting from scratch, and the install went fine.
Error:
TASK [wireguard : WireGuard repository configured] ***************************************************************
fatal: [13.58.93.167]: FAILED! => {"changed": false, "cmd": "apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 E1B39B6EF6DDB96564797591AE33835F504A1A25", "msg": "Warning: apt-key output should not be parsed (stdout is not a terminal)\ngpg: keyserver receive failed: No data", "rc": 2, "stderr": "Warning: apt-key output should not be parsed (stdout is not a terminal)\ngpg: keyserver receive failed: No data\n", "stderr_lines": ["Warning: apt-key output should not be parsed (stdout is not a terminal)", "gpg: keyserver receive failed: No data"], "stdout": "Executing: /tmp/apt-key-gpghome.XiSO86hQrl/gpg.1.sh --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 E1B39B6EF6DDB96564797591AE33835F504A1A25\n", "stdout_lines": ["Executing: /tmp/apt-key-gpghome.XiSO86hQrl/gpg.1.sh --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 E1B39B6EF6DDB96564797591AE33835F504A1A25"]}
jackivanov
commented
6 years ago Confirmed. The issue not really depends on us, but I'll make a workaround
OS / Environment (where do you run Algo on)
Cloud Provider (where do you deploy Algo to)
Summary of the problem
When installing the latest version of algo (version available 26 June 2018), the task
[dns_encryption : Add the repository]fails with the following error:Steps to reproduce the behavior
[dns_encryption : Add the repository]Full log