Package: vagrant
Version: 2.0.2+dfsg-2
Severity: normal
Tags: patch
Dear Maintainer,
After upgrading vagrant from version 1.9.1+dfsg-1 to 2.0.2+dfsg-2 on my stretch
machine, I tried running "vagrant up" only to find that my box could not be
started due to an invalid option for ruby-net-ssh:
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
==> default: Forcing shutdown of VM...
==> default: Destroying VM and associated drives...
/usr/lib/ruby/vendor_ruby/net/ssh.rb:204:in `start': invalid option(s):
verify_host_key (ArgumentError)
from
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:409:in
`block (2 levels) in connect'
from /usr/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
from /usr/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
from /usr/lib/ruby/2.3.0/timeout.rb:33:in `catch'
from /usr/lib/ruby/2.3.0/timeout.rb:33:in `catch'
from /usr/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
from
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:383:in
`block in connect'
from
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/retryable.rb:17:in
`retryable'
from
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:382:in
`connect'
from
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:83:in
`block in wait_for_ready'
from /usr/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
from /usr/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
from /usr/lib/ruby/2.3.0/timeout.rb:33:in `catch'
from /usr/lib/ruby/2.3.0/timeout.rb:33:in `catch'
from /usr/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
from
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:61:in
`wait_for_ready'
from
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/wait_for_communicator.rb:16:in
`block in call'
When troubleshooting this, I found bug #884104 and learned that I needed a
newer version of ruby-net-ssh, since my installed version (3.2.0-1) did not
support the option :verify_host_key. Installing version 4.2.0-2 fixed the
problem.
Please update the dependency on ruby-net-ssh to at least version 4.2.0. A
simple patch is attached.
-- System Information:
Debian Release: 9.3
APT prefers stable
APT policy: (990, 'stable'), (500, 'testing'), (110, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages vagrant depends on:
ii bsdtar 3.2.2-2
ii curl 7.52.1-5+deb9u4
ii openssh-client 1:7.4p1-10+deb9u2
ii ruby 1:2.3.3
ii ruby-childprocess 0.5.9-1
ii ruby-erubis 2.7.0-3
ii ruby-i18n 0.7.0-2
ii ruby-listen 3.0.3-3
ii ruby-log4r 1.1.10-4
ii ruby-net-scp 1.2.1-4
ii ruby-net-sftp 1:2.1.2-3
ii ruby-net-ssh 1:4.2.0-2
ii ruby-rest-client 1.8.0-3
Versions of packages vagrant recommends:
pn vagrant-libvirt <none>
Versions of packages vagrant suggests:
pn virtualbox <none>
-- no debconf information
--- debian/control.org 2018-02-17 14:06:27.721979518 +0100
+++ debian/control 2018-02-17 14:07:03.762463733 +0100
@@ -14,7 +14,7 @@
ruby-log4r (>= 1.1.9),
ruby-net-scp (>= 1.1.0),
ruby-net-sftp,
- ruby-net-ssh (>= 1:2.6.6),
+ ruby-net-ssh (>= 1:4.2.0),
ruby-rest-client,
Standards-Version: 4.1.3
Vcs-Git: https://salsa.debian.org/ruby-team/vagrant.git
@@ -36,7 +36,7 @@
ruby-log4r (>= 1.1.9),
ruby-net-scp (>= 1.1.0),
ruby-net-sftp,
- ruby-net-ssh (>= 1:2.6.6),
+ ruby-net-ssh (>= 1:4.2.0),
ruby-rest-client,
${misc:Depends},
${shlibs:Depends}
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
