You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RVM updated its install process by adding a GPG Key.
This does break the ansible role.
Here is the error:
failed: [default] => {"changed": false, "cmd": "/home/vagrant/.rvm/bin/rvm get stable && /home/vagrant/.rvm/bin/rvm reload", "delta": "0:00:55.607358", "end": "2014-10-29 10:15:04.945408", "rc": 1, "start": "2014-10-29 10:14:09.338050"}stderr: gpg: directory `/home/vagrant/.gnupg' createdgpg: new configuration file `/home/vagrant/.gnupg/gpg.conf' createdgpg: WARNING: options in `/home/vagrant/.gnupg/gpg.conf' are not yet active during this rungpg: keyring `/home/vagrant/.gnupg/pubring.gpg' createdgpg: Signature made Wed 29 Oct 2014 12:14:56 AM UTC using RSA key ID BF04FF17gpg: Can't check signature: public key not foundCould not update RVM, get some help at #rvm IRC channel at freenode servers.stdout: Downloading https://get.rvm.ioDownloading https://github.com/wayneeseguin/rvm/archive/1.25.34.tar.gzDownloading https://github.com/wayneeseguin/rvm/releases/download/1.25.34/1.25.34.tar.gz.ascERROR: GPG signature verification failed for '/home/vagrant/.rvm/archives/rvm-1.25.34.tgz' - 'https://github.com/wayneeseguin/rvm/releases/download/1.25.34/1.25.34.tar.gz.asc'!try downloading the signatures: gpg --keyserver hkp://keys.gnupg.net --recv-keys D39DC0E3 BF04FF17they can be compared with: https://rvm.io/mpapis.asc https://keybase.io/mpapisFATAL: all hosts have already failed -- aborting
In order to make it work again it will be perfect if you could add this command before executing the role:
Hello,
RVM updated its install process by adding a GPG Key.
This does break the ansible role.
Here is the error:
In order to make it work again it will be perfect if you could add this command before executing the role:
gpg --keyserver hkp://keys.gnupg.net --recv-keys D39DC0E3 BF04FF17
Thank you.
The text was updated successfully, but these errors were encountered: