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
I am a newbie. Hopefully someone can assist. thanks in advance
GPG error: http://ppa.launchpad.net trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5BB92C09DB82666C
local: WARNING: The following packages cannot be authenticated!
python2.7 libpython2.7 libpython2.7-stdlib python2.7-minimal
local: libpython2.7-minimal
local: E
local: :
local: There are problems and -y was used without --force-yes
local: deployment/ansible.sh: line 52: pip: command not found
local: Python 2.7.6
local: Running Ansible provisioner defined in Vagrantfile.
local: deployment/ansible.sh: line 76: ansible-playbook: command not found
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
The text was updated successfully, but these errors were encountered:
I am a newbie. Hopefully someone can assist. thanks in advance
GPG error: http://ppa.launchpad.net trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5BB92C09DB82666C
local: WARNING: The following packages cannot be authenticated!
python2.7 libpython2.7 libpython2.7-stdlib python2.7-minimal
local: libpython2.7-minimal
local: E
local: :
local: There are problems and -y was used without --force-yes
local: deployment/ansible.sh: line 52: pip: command not found
local: Python 2.7.6
local: Running Ansible provisioner defined in Vagrantfile.
local: deployment/ansible.sh: line 76: ansible-playbook: command not found
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
The text was updated successfully, but these errors were encountered: