I started over from scratch, and got past the ssh auth errors I was seeing when running `vagrant up`.
However, I'm still getting the same "SCP did not finish successfully" error when trying to run `vagrant hostmanager`. I haven't bothered trying to update the Vagrantfile with the hostmanager related settings, since running `vagrant hostmanager` is failing on the command line. Any tips on how to debug this issue? On Tuesday, December 16, 2014 8:16:21 AM UTC-8, Traun Leyden wrote: > > > After digging in further, it looks like I'm having ssh auth issues as > described here > <http://stackoverflow.com/questions/24867490/coreos-authentication-failure-on-vagrant-up?rq=1>, > > and the posted solution isn't working for me, so it's probably not an issue > with the vagrant-hostmanager plugin. > > I'll update the thread if I get anywhere. > > > On Tuesday, December 16, 2014 7:30:46 AM UTC-8, Traun Leyden wrote: >> >> >> I'm running the latest Vagrant (v 1.7.1) and running a 3 node CoreOS >> cluster based on the CoreOS + Vagrant docs >> <https://coreos.com/docs/running-coreos/platforms/vagrant/>. >> >> After installing the the vagrant-hostmanager plugin, and running "vagrant >> up" to kick off my cluster, I'm running: >> >> $ vagrant hostmanager >> >> and getting this error: >> >> $ vagrant hostmanager >> [core-01] Updating /etc/hosts file... >> /opt/vagrant/embedded/gems/gems/net-scp-1.1.2/lib/net/scp.rb:359:in >> `block (3 levels) in start_command': SCP did not finish successfully (1) >> (Net::SCP::Error) >> from >> /opt/vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/channel.rb:591:in >> >> `call' >> from >> /opt/vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/channel.rb:591:in >> >> `do_close' >> from >> /opt/vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:586:in >> >> `channel_close' >> from >> /opt/vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:465:in >> >> `dispatch_incoming_packets' >> from >> /opt/vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:221:in >> >> `preprocess' >> from >> /opt/vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:205:in >> >> `process' >> from >> /opt/vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:169:in >> >> `block in loop' >> from >> /opt/vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:169:in >> >> `loop' >> from >> /opt/vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:169:in >> >> `loop' >> from >> /opt/vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/channel.rb:269:in >> >> `wait' >> from /opt/vagrant/embedded/gems/gems/net-scp-1.1.2/lib/net/scp.rb:316:in >> `download!' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/plugins/communicators/ssh/communicator.rb:253:in >> >> `block in download' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/plugins/communicators/ssh/communicator.rb:615:in >> >> `block in scp_connect' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/plugins/communicators/ssh/communicator.rb:312:in >> >> `connect' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/plugins/communicators/ssh/communicator.rb:613:in >> >> `scp_connect' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/plugins/communicators/ssh/communicator.rb:252:in >> >> `download' >> from >> /Users/tleyden/.vagrant.d/gems/gems/vagrant-hostmanager-1.5.0/lib/vagrant-hostmanager/hosts_file.rb:25:in >> >> `update_guest' >> from >> /Users/tleyden/.vagrant.d/gems/gems/vagrant-hostmanager-1.5.0/lib/vagrant-hostmanager/action/update_guest.rb:29:in >> >> `call' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/action/warden.rb:34:in >> >> `call' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/action/builtin/config_validate.rb:25:in >> >> `call' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/action/warden.rb:34:in >> >> `call' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/action/builder.rb:116:in >> >> `call' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/action/runner.rb:66:in >> >> `block in run' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/util/busy.rb:19:in >> `busy' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/action/runner.rb:66:in >> >> `run' >> from >> /Users/tleyden/.vagrant.d/gems/gems/vagrant-hostmanager-1.5.0/lib/vagrant-hostmanager/command.rb:25:in >> >> `block in execute' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/plugin/v2/command.rb:226:in >> >> `block in with_target_vms' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/plugin/v2/command.rb:220:in >> >> `each' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/plugin/v2/command.rb:220:in >> >> `with_target_vms' >> from >> /Users/tleyden/.vagrant.d/gems/gems/vagrant-hostmanager-1.5.0/lib/vagrant-hostmanager/command.rb:24:in >> >> `execute' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/cli.rb:42:in >> `execute' >> from >> /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/environment.rb:301:in >> >> `cli' >> from >> /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.7.1/bin/vagrant:174:in >> `<main>' >> >> Is this a bug or am I doing something wrong? >> >> According to this post >> <https://groups.google.com/d/msg/coreos-user/Dkl0Rj3Rg6w/U-FsBsbrziwJ> >> on the CoreOS list, other users have gotten vagrant-hostmanager + CoreOS >> working. >> > > -- 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]. For more options, visit https://groups.google.com/d/optout.
