`TASK [gpg : Refresh the Streisand GPG keyring with keyserver information] ***************************
FAILED - RETRYING: Refresh the Streisand GPG keyring with keyserver information (10 retries left).
FAILED - RETRYING: Refresh the Streisand GPG keyring with keyserver information (9 retries left).
FAILED - RETRYING: Refresh the Streisand GPG keyring with keyserver information (8 retries left).
FAILED - RETRYING: Refresh the Streisand GPG keyring with keyserver information (7 retries left).
FAILED - RETRYING: Refresh the Streisand GPG keyring with keyserver information (6 retries left).
FAILED - RETRYING: Refresh the Streisand GPG keyring with keyserver information (5 retries left).
FAILED - RETRYING: Refresh the Streisand GPG keyring with keyserver information (4 retries left).
FAILED - RETRYING: Refresh the Streisand GPG keyring with keyserver information (3 retries left).
FAILED - RETRYING: Refresh the Streisand GPG keyring with keyserver information (2 retries left).
FAILED - RETRYING: Refresh the Streisand GPG keyring with keyserver information (1 retries left).
fatal: [localhost]: FAILED! => {"attempts": 10, "changed": true, "cmd": ["gpg2", "--no-default-keyring", "--keyring", "/root/.gnupg/streisand/pubring.gpg", "--keyserver-options", "timeout=120", "--refresh"], "delta": "0:00:01.791486", "end": "2018-07-16 11:25:19.513836", "msg": "non-zero return code", "rc": 2, "start": "2018-07-16 11:25:17.722350", "stderr": "gpg: refreshing 10 keys from hkps://hkps.pool.sks-keyservers.net\ngpg: keyserver refresh failed: General error", "stderr_lines": ["gpg: refreshing 10 keys from hkps://hkps.pool.sks-keyservers.net", "gpg: keyserver refresh failed: General error"], "stdout": "", "stdout_lines": []}
to retry, use: --limit @/streisand/playbooks/localhost.retry
PLAY RECAP ************************************************
localhost : ok=40 changed=9 unreachable=0 failed=1
(venv) root@vpnaxeltest:/streisand#
`
ansible --version :(venv) root@vpnaxeltest:/streisand# ansible --version
ansible 2.5.4
config file = /streisand/ansible.cfg
configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /streisand/venv/local/lib/python2.7/site-packages/ansible
executable location = /streisand/venv/bin/ansible
python version = 2.7.12 (default, Dec 4 2017, 14:50:18) [GCC 5.4.0 20160609]
(venv) root@vpnaxeltest:/streisand#
@hexicans Sorry to see you're having an issue running the script. This type of error is transient in nature, have you tried running it again?
@alimakki Yes but doesn't work... if you have SSH key, i can give you SSH access. Please :-)
If you want to force this step, edit playbooks/roles/gpg/tasks/main.yml line 89 to when: False.
Hello,
Thanks, i test
De : Jay Carlson notifications@github.com
Envoyé : mardi 17 juillet 2018 00:55
À : StreisandEffect/streisand streisand@noreply.github.com
Cc : hexicans Axel@dyjix.eu; Mention mention@noreply.github.com
Objet : Re: [StreisandEffect/streisand] Problem in install (#1406)
If you want to force this step, edit https://github.com/StreisandEffect/streisand/blob/0831994158e302a719ed47389bcaeb85970a03ba/playbooks/roles/gpg/tasks/main.yml#L89 playbooks/roles/gpg/tasks/main.yml line 89 to when: False.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/StreisandEffect/streisand/issues/1406#issuecomment-405405863 , or mute the thread https://github.com/notifications/unsubscribe-auth/AM5Tuy6_r6k8flnPgll2AOTGJkyqchPPks5uHRmsgaJpZM4VRVpy . https://github.com/notifications/beacon/AM5Tu5U1X8HzjmeOCRFgQgzf5c9LgWq3ks5uHRmsgaJpZM4VRVpy.gif
@hexicans I would also recommend running Streisand against one of the supported providers, OpenVZ servers have had issues in the past.
Hello,
Yes i will test with kvm server. Thanks for « false », it fix.
Do you know if work in LXC server ?
De : Ali Makki notifications@github.com
Envoyé : mardi 17 juillet 2018 15:23
À : StreisandEffect/streisand streisand@noreply.github.com
Cc : hexicans Axel@dyjix.eu; Mention mention@noreply.github.com
Objet : Re: [StreisandEffect/streisand] Problem in install (#1406)
@hexicans https://github.com/hexicans I would also recommend running Streisand against one of the supported providers, OpenVZ servers have had issues in the past.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/StreisandEffect/streisand/issues/1406#issuecomment-405579662 , or mute the thread https://github.com/notifications/unsubscribe-auth/AM5Tu7ngeNaALp3IK6VRpjrj6BJ_SEO4ks5uHeUkgaJpZM4VRVpy . https://github.com/notifications/beacon/AM5Tu5CwFk49Ssl42tXUmDeikKaPW78nks5uHeUkgaJpZM4VRVpy.gif
We use LXC for travis, so this should be possible. Just keep in mind that if you plan to use WireGuard, the host OS where LXC will be running will require the WireGuard kernel modules compiled and installed as well.
I'm going to close this, since it sounds like things are working now. Please reopen if that's not the case.
That server is down, is there another one we can use?
Having the same problem now, Aug 9th. Re-tried to run the script three times. Will use work-around for now.
It worked well repeatedly the last days Aug 5th - Aug 8th.
never run into this issue before, but running into it repeatedly today. my VPS went down earlier, which i'm _guessing_ is due to the cron job that refreshes the keyring every day, & now i'm also unable to reprovision for the same reason. using a Lunanode server, never had this issue in the past.
what are the long-term consequences of running w/ when: false for both of these tasks?
i got this problem.
i let streisand set up the aws server to cut me out of the process and yet it is still giving this message
Experienced the same error on an AWS EC2 instance, with the following details:
ubuntu@redacted:~$ uname -a
Linux ip-172-31-24-7 4.15.0-1039-aws #41-Ubuntu SMP Wed May 8 10:43:54 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@redacted:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
both builder and streisand server are EC2 instances.
I did not know streisand even supported 1804 I thought it had to be
1604.
On Mon, 08 Jul 2019 11:15:55 -0400,
jowa wrote:
[1
[2 Experienced the same error on an AWS EC2 instance, with the following details: ubuntu@ip-172-31-24-7:~$ uname -a
Linux ip-172-31-24-7 4.15.0-1039-aws #41-Ubuntu SMP Wed May 8 10:43:54 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@ip-172-31-24-7:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic―
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici wb2una
[email protected]
Hmm not sure, I can't seem to find that 1604 is required.
Also experiencing this from Digital Ocean NYC 1.
Just cloned streisand and it hangs on TASK [gpg : Refresh the Streisand GPG keyring with keyserver information] ****** using DO NYC 3.
same here with @belmarca on DO Frankfurt
GPG issues seem to be working now. Fixed in #1604. Could you do another pull and try again? If it's blowing up on the GPG stage still, I would love to find out about it.
@jowabels, I filed PR #1606 to make clear that the localhost/remote system must be running Ubuntu 16.04. Thanks for the catch.
Thank you so much @nopdotcom
@nopdotcom: I experienced this same GPG refresh failed issue while running ./streisand locally (MacOS) to setup a Wireguard server on GCP.
Streisand is creating an Ubuntu 16.04 image on GCP (ubuntu-1604-xenial-v20200807), which seems to conform to the requirements clarified in PR #1606 .
I am able to bypass the issue using the "when: False" edit you suggested on playbooks/roles/gpg/tasks/main.yml line 89. But that seems like a workaround that should not be necessary?
Additional information:
Enabled Roles
Should I open a new issue?
Most helpful comment
@nopdotcom: I experienced this same GPG refresh failed issue while running ./streisand locally (MacOS) to setup a Wireguard server on GCP.
Streisand is creating an Ubuntu 16.04 image on GCP (ubuntu-1604-xenial-v20200807), which seems to conform to the requirements clarified in PR #1606 .
I am able to bypass the issue using the "when: False" edit you suggested on playbooks/roles/gpg/tasks/main.yml line 89. But that seems like a workaround that should not be necessary?
Additional information:
Enabled Roles
Should I open a new issue?