"up" fails but then the VM is up and running

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

"up" fails but then the VM is up and running

Gianfranco Cecconi
When I vagrant up a vanilla fedora/25-cloud-base system, it fails by showing me this:

(...)
==> default: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

# Down the interface before munging the config file. This might
# fail if the interface is not actually set up yet so ignore
# errors.
/sbin/ifdown 'eth1' || true

# Move new config into place
mv
'/tmp/vagrant-network-entry-eth1-1496601950-0' '/etc/sysconfig/network-scripts/ifcfg-eth1'

# Bring the interface up
ARPCHECK
=no /sbin/ifup 'eth1'

Stdout from the command:

Determining IP information for eth1... failed.

Stderr from the command:

usage
: ifdown <configuration>
$

But then I do vagrant ssh and I am in.

$ ifconfig -a
eth0
: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet
192.168.121.107  netmask 255.255.255.0  broadcast 192.168.121.255
        inet6 fe80
::5054:ff:fec7:4c89  prefixlen 64  scopeid 0x20<link>
        ether
52:54:00:c7:4c:89  txqueuelen 1000  (Ethernet)
        RX packets
514  bytes 64858 (63.3 KiB)
        RX errors
0  dropped 2  overruns 0  frame 0
        TX packets
366  bytes 51476 (50.2 KiB)
        TX errors
0  dropped 0 overruns 0  carrier 0  collisions 0

eth1
: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80
::5054:ff:fe52:4b9d  prefixlen 64  scopeid 0x20<link>
        ether
52:54:00:52:4b:9d  txqueuelen 1000  (Ethernet)
        RX packets
54  bytes 6090 (5.9 KiB)
        RX errors
0  dropped 0  overruns 0  frame 0
        TX packets
15  bytes 3042 (2.9 KiB)
        TX errors
0  dropped 0 overruns 0  carrier 0  collisions 0

lo
: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet
127.0.0.1  netmask 255.0.0.0
        inet6
::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen
1  (Local Loopback)
        RX packets
0  bytes 0 (0.0 B)
        RX errors
0  dropped 0  overruns 0  frame 0
        TX packets
0  bytes 0 (0.0 B)
        TX errors
0  dropped 0 overruns 0  carrier 0  collisions 0
$

The Vagrantfile specifies

config.vm.network :public_network, :bridge => 'wlp3s0', :dev => 'wlp3s0'

where wlp3s0 is my Thinkpad's WiFi interface. Something is not working anyway as the IPs are not valid in my network. Can you give me any hints on what is going wrong here? Thanks.

G.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/0423dcf7-df11-40f9-9806-39769b44b3bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: "up" fails but then the VM is up and running

Alvaro Miranda Aguilera
hello

vagrant version
vagrant plugin list
host os

?

it seems is somethinng between virtualbox and the router not giving dhcp since wlan doesn't seem to support promisc


if i manually do

ifconfig eth1 up

i get dhcov6 and ipv6 just fine

if i do 

dhclient -4 -d eth1

no joy

more info here:

https://www.virtualbox.org/manual/ch06.html#network_bridged


if you do vagrant halt


turn the vm over virtualbox gui, and works, then it  would be a vagrant issue, but seems more a wlan in general limitation


Alvaro





On Sun, Jun 4, 2017 at 9:11 PM, Gianfranco Cecconi <[hidden email]> wrote:
When I vagrant up a vanilla fedora/25-cloud-base system, it fails by showing me this:

(...)
==> default: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

# Down the interface before munging the config file. This might
# fail if the interface is not actually set up yet so ignore
# errors.
/sbin/ifdown 'eth1' || true

# Move new config into place
mv
'/tmp/vagrant-network-entry-eth1-1496601950-0' '/etc/sysconfig/network-scripts/ifcfg-eth1'

# Bring the interface up
ARPCHECK
=no /sbin/ifup 'eth1'

Stdout from the command:

Determining IP information for eth1... failed.

Stderr from the command:

usage
: ifdown <configuration>
$

But then I do vagrant ssh and I am in.

$ ifconfig -a
eth0
: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet
192.168.121.107  netmask 255.255.255.0  broadcast 192.168.121.255
        inet6 fe80
::5054:ff:fec7:4c89  prefixlen 64  scopeid 0x20<link>
        ether
52:54:00:c7:4c:89  txqueuelen 1000  (Ethernet)
        RX packets
514  bytes 64858 (63.3 KiB)
        RX errors
0  dropped 2  overruns 0  frame 0
        TX packets
366  bytes 51476 (50.2 KiB)
        TX errors
0  dropped 0 overruns 0  carrier 0  collisions 0

eth1
: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80
::5054:ff:fe52:4b9d  prefixlen 64  scopeid 0x20<link>
        ether
52:54:00:52:4b:9d  txqueuelen 1000  (Ethernet)
        RX packets
54  bytes 6090 (5.9 KiB)
        RX errors
0  dropped 0  overruns 0  frame 0
        TX packets
15  bytes 3042 (2.9 KiB)
        TX errors
0  dropped 0 overruns 0  carrier 0  collisions 0

lo
: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet
127.0.0.1  netmask 255.0.0.0
        inet6
::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen
1  (Local Loopback)
        RX packets
0  bytes 0 (0.0 B)
        RX errors
0  dropped 0  overruns 0  frame 0
        TX packets
0  bytes 0 (0.0 B)
        TX errors
0  dropped 0 overruns 0  carrier 0  collisions 0
$

The Vagrantfile specifies

config.vm.network :public_network, :bridge => 'wlp3s0', :dev => 'wlp3s0'

where wlp3s0 is my Thinkpad's WiFi interface. Something is not working anyway as the IPs are not valid in my network. Can you give me any hints on what is going wrong here? Thanks.

G.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/0423dcf7-df11-40f9-9806-39769b44b3bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezhs2aXq6ccft71L%2BfBYaRDfFQfy01%3DTQLgTsE3P6GmUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.