This repository has been archived by the owner on Feb 11, 2022. It is now read-only.
Vagrant aws terminates instance at startup after rsync. #98
Comments
|
Seems like a duplicate of #72 . |
|
I think it's separate from #72 . Fixing the tty permission issue still gives this error. I'm also using RubyInstaller 193 on Windows. |
|
Looking at the logging, I'd guess the problem is that the plugin shells out to the rsync command, which isn't going to be present on Windows. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Vagrant AWS on windows using RubyInstaller Ruby 193 and same issue Ruby 187.
DEBUG ssh: == Net-SSH connection debug-level log END ==
INFO ssh: SSH is ready!
INFO run_instance: Time for SSH ready: 16.245227098464966
INFO interface: info: Machine is booted and ready for use!
[default] Machine is booted and ready for use!
INFO machine: Calling action: read_ssh_info on provider AWS (i-fd4c9f90)
INFO runner: Running action: #Vagrant::Action::Builder:0x2ade2d0
INFO warden: Calling action: #<Vagrant::Action::Builtin::ConfigValidate:0x2aa28
58>
INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ConnectAWS:0x2aa276
8>
INFO connect_aws: Connecting to AWS...
INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ReadSSHInfo:0x2f2dc
58>
INFO interface: info: Rsyncing folder: C:/repository/vagrant/base/ => /vagrant
[default] Rsyncing folder: C:/repository/vagrant/base/ => /vagrant
DEBUG ssh: Re-using SSH connection.
INFO ssh: Execute: mkdir -p '/vagrant' (sudo=true)
DEBUG ssh: stderr: stdin: is not a tty
DEBUG ssh: Exit status: 0
DEBUG ssh: Re-using SSH connection.
INFO ssh: Execute: chown ubuntu '/vagrant' (sudo=true)
DEBUG ssh: stderr: stdin: is not a tty
DEBUG ssh: Exit status: 0
INFO subprocess: Starting process: ["rsync", "--verbose", "--archive", "-z", "-
-exclude", ".vagrant/", "-e", "ssh -p 22 -o StrictHostKeyChecking=no -i 'C:/repo
sitory/keys/us_east.pem'", "C:/repository/vagrant/base/",
"[email protected]:/vagrant"]
ERROR warden: Error occurred: Unknown error (Windows says "The operation complet
ed successfully.", but it did not.)
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<VagrantPlugins::AWS::Action::RunInstance:0x3134
838>
INFO machine: Calling action: read_state on provider AWS (i-fd4c9f90)
INFO runner: Running action: #Vagrant::Action::Builder:0x2ad0878
INFO warden: Calling action: #<Vagrant::Action::Builtin::ConfigValidate:0x2aa51
08>
INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ConnectAWS:0x2aa50c
0>
INFO connect_aws: Connecting to AWS...
INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ReadState:0x2f1fa50
The text was updated successfully, but these errors were encountered: