Its a top priority to fix. You can expect a fix in 1.6.1 this week. I apologize for this. Luckily, there are no internal state changes between 1.5 and 1.6. I'd recommend downgrading for now.
On Tue, May 6, 2014 at 1:01 PM, Chris Handy <chrisjha...@gmail.com> wrote: > Multiple people are getting it > > https://github.com/mitchellh/vagrant/issues/3649 > > > On Tuesday, May 6, 2014 3:51:36 PM UTC-4, Felipe Salum wrote: >> >> It was working fine on Vagrant 1.5.x. Do I need to change something on my >> Vagrantfile ? >> >> ==> dev-001: Configuring and enabling network interfaces... >> The following SSH command responded with a non-zero exit status. >> Vagrant assumes that this means the command failed! >> >> /sbin/ifdown >> >> Stdout from the command: >> >> >> >> Stderr from the command: >> >> usage: ifdown <device name> >> >> This is the network part on my Vagrantfile: >> n.vm.network "private_network", ip: opts[:ip] >> >> Thanks, >> Felipe >> > -- > 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 vagrant-up+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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 vagrant-up+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
