Yeah think I am going to update the instructions to say ONLY 1.8.4 On Oct 20, 2016 13:47, "Steve Kuznetsov" <[email protected]> wrote:
> Are you able to work around the issue with Vagrant 1.8.4? > > On Thu, Oct 20, 2016 at 4:10 AM, Frans Thamura <[email protected]> wrote: > >> My vagrant is 1.8.5 >> >> On Oct 11, 2016 00:25, "Steven Pousty" <[email protected]> wrote: >> >>> My guess is your are using the version of Vagrant with the bug. >>> >>> " >>> >>> - Vagrant <https://www.vagrantup.com/downloads.html> (may also be >>> offered in your distro) - We have tested with 1.7.2, 1.7.4. Right now we >>> are seeing a BAD SSH bug with 1.8.5, please get Vagrant 1.8.4 >>> <https://releases.hashicorp.com/vagrant/1.8.4/> >>> >>> " >>> >>> On Mon, Oct 10, 2016 at 10:17 AM, Steve Kuznetsov <[email protected]> >>> wrote: >>> >>>> Ah, you are using the All-In-One. I'm not familiar with that image, >>>> ccing Steve Pousty who I believe will know more. >>>> >>>> Steve >>>> >>>> On Oct 10, 2016 12:40 AM, "Frans Thamura" <[email protected]> wrote: >>>> >>>>> Hi Steve >>>>> >>>>> I follow this instruction >>>>> >>>>> vagrant init openshift/origin-all-in-one >>>>> >>>>> vagrant up --provider=virtualbox >>>>> >>>>> >>>>> -- >>>>> Frans Thamura (曽志胜) >>>>> Java Champion >>>>> Shadow Master and Lead Investor >>>>> Meruvian. >>>>> Integrated Hypermedia Java Solution Provider. >>>>> >>>>> Mobile: +628557888699 >>>>> Blog: http://blogs.mervpolis.com/roller/flatburger (id) >>>>> >>>>> FB: http://www.facebook.com/meruvian >>>>> TW: http://www.twitter.com/meruvian / @meruvian >>>>> Website: http://www.meruvian.org >>>>> >>>>> "We grow because we share the same belief." >>>>> >>>>> >>>>> On Sat, Oct 1, 2016 at 11:45 PM, Steve Kuznetsov <[email protected]> >>>>> wrote: >>>>> > You are attempting to use the Vagrantfile in the Origin repository? >>>>> > >>>>> > Could you link the output of the following commands, issued with the >>>>> Origin >>>>> > repository as the working directory? >>>>> > >>>>> > $ git log --oneline -n 1 >>>>> > $ vagrant destroy --force >>>>> > $ rm -rf .vagrant >>>>> > $ vagrant up --provider=virtualbox --debug >>>>> > >>>>> > Steve >>>>> > >>>>> > >>>>> > On Oct 1, 2016 6:28 AM, "Frans Thamura" <[email protected]> wrote: >>>>> >> >>>>> >> I have ssh using user "vagrant" private key problem >>>>> >> >>>>> >> Auth cannot be done >>>>> >> >>>>> >> >>>>> >> F >>>>> >> -- >>>>> >> Frans Thamura (曽志胜) >>>>> >> Java Champion >>>>> >> Shadow Master and Lead Investor >>>>> >> Meruvian. >>>>> >> Integrated Hypermedia Java Solution Provider. >>>>> >> >>>>> >> Mobile: +628557888699 >>>>> >> Blog: http://blogs.mervpolis.com/roller/flatburger (id) >>>>> >> >>>>> >> FB: http://www.facebook.com/meruvian >>>>> >> TW: http://www.twitter.com/meruvian / @meruvian >>>>> >> Website: http://www.meruvian.org >>>>> >> >>>>> >> "We grow because we share the same belief." >>>>> >> >>>>> >> >>>>> >> On Sat, Oct 1, 2016 at 5:19 PM, Budh Gurung <[email protected]> >>>>> wrote: >>>>> >> > Hi Frans, >>>>> >> > >>>>> >> > On Sat, Oct 1, 2016 at 3:10 PM, Frans Thamura <[email protected] >>>>> > >>>>> >> > wrote: >>>>> >> >> >>>>> >> >> I try OpenShift 1.3 Origin >>>>> >> >> >>>>> >> >> got this error >>>>> >> >> >>>>> >> >> ervo@Mervium:~/openshift$ vagrant up --provider=virtualbox >>>>> >> >> Bringing machine 'default' up with 'virtualbox' provider... >>>>> >> >> ==> default: Checking if box 'openshift/origin-all-in-one' is up >>>>> to >>>>> >> >> date... >>>>> >> >> ==> default: Running provisioner: shell... >>>>> >> >> SSH authentication failed! This is typically caused by the >>>>> >> >> public/private >>>>> >> >> keypair for the SSH user not being properly set on the guest VM. >>>>> Please >>>>> >> >> verify that the guest VM is setup with the proper public key, >>>>> and that >>>>> >> >> the private key path for Vagrant is setup properly as well. >>>>> >> >> >>>>> >> > >>>>> >> > Which version of vagrant you are using? There is issue related to >>>>> >> > authentication [1] in vagrant. >>>>> >> > >>>>> >> > In most of the cases, clean removal of current virtual machine >>>>> instance >>>>> >> > works. i.e >>>>> >> > vagrant destroy; rm -rf .vagrant >>>>> >> > >>>>> >> > It still you are having issues, need more info like debug logs ( >>>>> >> > vagrant up >>>>> >> > --provider=virtualbox --debug ) >>>>> >> > >>>>> >> > [1] https://github.com/mitchellh/vagrant/issues/7732 >>>>> >> > >>>>> >> >> can help why? >>>>> >> >> >>>>> >> >> >>>>> >> >> F >>>>> >> >> >>>>> >> >> _______________________________________________ >>>>> >> >> dev mailing list >>>>> >> >> [email protected] >>>>> >> >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >>>>> >> > >>>>> >> > >>>>> >> > Regards, >>>>> >> > Budh Ram Gurung >>>>> >> > Software Engineer - Dev Tools >>>>> >> >>>>> >> _______________________________________________ >>>>> >> dev mailing list >>>>> >> [email protected] >>>>> >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >>>>> >>>> >>> >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
