Re: [vagrant-up] The SSH command responded with a non-zero exit status.

i think the playbook ( not sure if puppet or ansible there) is failing. I suggest: - vagrant destroy - vagrant up --no-provision that should work. then vagrant provision will fail per log. that will help to visualize is not a vagrant issue but a provisioning issue. you can work on the

Re: [vagrant-up] proposal for winrm connection, presigned insecure cert

Hey there, Thank you Pixel Fairy for reporting this improvement request. Thank you Alvaro and Mário for your useful inputs. Ansible support for Windows has without any doubt strongly evolved since late 2015, which is the time when the WinRM support was added to the Ansible provisioner in

Re: [vagrant-up] GUI Tests: This operation requires an interactive window station

Thanks so much Jordan! I didn't know this command, I'm able to run my tests and interact with the GUI. El lunes, 14 de mayo de 2018, 6:27:56 (UTC+2), Jordan Borean escribió: > > You're easiest option is to use something like psexec to launch the > process under an interactive logon, to do

Re: [vagrant-up] Vagrant Cloud Upload Large Files

Had that problem in the past, and could only upload using aws and a mv. To uploaded to S3 with chunks with a tool that I don’t remember now ... On Tue, May 15, 2018 at 7:18 AM, Jordan Borean wrote: > Hi > > Sorry if this isn't the right area to ask this but I upload some

[vagrant-up] Vagrant Cloud Upload Large Files

Hi Sorry if this isn't the right area to ask this but I upload some large vagrant boxes to Vagrant Cloud on a somewhat regular basis and was wondering if there was a way to upload the box in smaller chunks instead of one big go. I find that I regularly get failures when uploading and that