Hi Vagrants!!
I am experiencing an issue which reproduces randomly (once every few
deployments).
Looks like Vagrant tries to SSH connect to the new VM unsuccessfully.
Take into account that the problem reproduces for VMs created from boxes
that already succeeded to deploy and connect in the past on top of the same
vCloud Director.
I am using Vagrant 1.7.4 deploying using the the vcloud plugin.
When I try to connect the same VM manually (after the failure) using the
password, I successfully login the VM.
Any clue what's going on? Is this s timing issue? Is there any retry
parameter which can be increased?
/opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh/prompt.rb:73:in
`prompt': undefined method `chomp' for nil:NilClass (NoMethodError)
from
/opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh/authentication/methods/password.rb:57:in
`ask_password'
from
/opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh/authentication/methods/password.rb:22:in
`authenticate'
from
/opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh/authentication/session.rb:79:in
`block in authenticate'
from
/opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh/authentication/session.rb:66:in
`each'
from
/opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh/authentication/session.rb:66:in
`authenticate'
from
/opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh.rb:211:in `start'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/communicator.rb:389:in
`block (2 levels) in connect'
from /opt/vagrant/embedded/lib/ruby/2.0.0/timeout.rb:66:in `timeout'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/communicator.rb:367:in
`block in connect'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/retryable.rb:17:in
`retryable'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/communicator.rb:366:in
`connect'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/communicator.rb:64:in
`block in wait_for_ready'
from /opt/vagrant/embedded/lib/ruby/2.0.0/timeout.rb:66:in `timeout'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/communicator.rb:42:in
`wait_for_ready'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/wait_for_communicator.rb:16:in
`block in call'
stdout: Bringing machine 'vAppName' up with 'vcloud' provider...
==> vAppName: Building vApp...
==> vAppName: vApp vAppName successfully created.
==> vAppName: Setting VM hardware...
==> vAppName: Powering on VM...
==> vAppName: Waiting for machine to boot. This may take a few minutes...
==> vAppName: Waiting for SSH Access on 10.153.164.94:22 ...
==> vAppName: Waiting for SSH Access on 10.153.164.94:22 ...
==> vAppName: Waiting for SSH Access on 10.153.164.94:22 ...
==> vAppName: Waiting for SSH Access on 10.153.164.94:22 ...
==> vAppName: Waiting for SSH Access on 10.153.164.94:22 ...
==> vAppName: Waiting for SSH Access on 10.153.164.94:22 ...
vAppName: SSH address: 10.153.164.94:22
vAppName: SSH username: root
vAppName: SSH auth method: password
[email protected]'s password:
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/e49063b7-e9f1-4db3-ac07-de599ef88979%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
