develpr commented on issue #3431: Vagrant provisioning results in 
SSLV3_ALERT_BAD_CERTIFICATE and failure to ping
   @chetanmeh sorry you're right, and I just took a look at the diff and bumped 
the version of ansible in my local version. That does seem to have resolved 
that issue, though I now end up with:
   default: set_fact 
---------------------------------------------------------------- 0.04s
       default: set_fact 
---------------------------------------------------------------- 0.04s
       default: set_fact 
---------------------------------------------------------------- 0.03s
       default: ++ sudo su -c 'mkdir ${HOME}/bin'
       default: ++ sudo su -c 'ln -s ${OPENWHISK_HOME}/tools/admin/wskadmin 
       default: ++ sudo su -c 'ln -s ${OPENWHISK_HOME}/tools/build/redo 
       default: ++ echo /home/vagrant/openwhisk/bin/wsk -i '"$@"'
       default: /tmp/vagrant-shell: line 22: /home/vagrant/bin/wsk: No such 
file or directory
   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.
   I think that the spirit of my issue is solved in reality and I should 
probably open a new ticket. (though I won't complain if anybody has any 
pro-tips to add here about this ;)). 
   Thank you very much all for a quick reply response! 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

Reply via email to