[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Impossible to restart vagrant VM after one vagrant halt



I think it's virtualbox port forwarding issue. Port forwarding isn't reloaded after vagrant up :(

I don't understand, I've this bug only with OpenShift vagrant VMs.

2016-01-29 10:44 GMT+01:00 Stéphane Klein <contact stephane-klein info>:
With export VAGRANT_LOG=debug

```
DEBUG ssh: Exit status: 0
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute: cat /sys/class/net/br0/address (sudo=true)
DEBUG ssh: stdout: b2:01:53:c2:19:49

DEBUG ssh: Exit status: 0
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute: cat /sys/class/net/eth0/address (sudo=true)
DEBUG ssh: stdout: 52:54:00:d3:eb:a4

DEBUG ssh: Exit status: 0
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute: cat /sys/class/net/eth1/address (sudo=true)
DEBUG ssh: stdout: 08:00:27:55:dc:63

DEBUG ssh: Exit status: 0
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute: cat /sys/class/net/ovs-system/address (sudo=true)
DEBUG ssh: stdout: 3a:69:03:e5:bb:21

DEBUG ssh: Exit status: 0
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute: cat /sys/class/net/tun0/address (sudo=true)
DEBUG ssh: stdout: 76:87:d8:0b:2a:c1

DEBUG ssh: Exit status: 0
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute: touch /etc/sysconfig/network-scripts/ifcfg-eth0 (sudo=true)
DEBUG ssh: Exit status: 0
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute: sed -e '/^#VAGRANT-BEGIN/,/^#VAGRANT-END/ d' /etc/sysconfig/network-scripts/ifcfg-eth0 > /tmp/vagrant-ifcfg-eth0 (sudo=true)
DEBUG ssh: Exit status: 0
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute: cat /tmp/vagrant-ifcfg-eth0 > /etc/sysconfig/network-scripts/ifcfg-eth0 (sudo=true)
DEBUG ssh: Exit status: 0
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute: rm -f /tmp/vagrant-ifcfg-eth0 (sudo=true)
DEBUG ssh: Exit status: 0
DEBUG ssh: Uploading: /var/folders/7v/bs1393w960b4_g1_2b5h9sf00000gn/T/vagrant20160129-84797-zndzbs to /tmp/vagrant-network-entry_eth0
DEBUG ssh: Re-using SSH connection.
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute: cat /tmp/vagrant-network-entry_eth0 >> /etc/sysconfig/network-scripts/ifcfg-eth0

if command -v nmcli &>/dev/null; then
  if command -v systemctl &>/dev/null && systemctl -q is-enabled NetworkManager &>/dev/null; then
    nmcli c reload eth0
  elif command -v service &>/dev/null && service NetworkManager status &>/dev/null; then
    nmcli c reload eth0
  fi
fi

/sbin/ifdown eth0
/sbin/ifup eth0

rm -f /tmp/vagrant-network-entry_eth0
 (sudo=true)
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
```

2016-01-29 10:37 GMT+01:00 Stéphane Klein <contact stephane-klein info>:
Hi,

what I did :

```
$ git clone git github com:openshift/openshift-ansible.git
$ cd openshift-ansible
$ vagrant up --no-provision
$ vagrant provision
$ vagrant status
node1                     running (virtualbox)
node2                     running (virtualbox)
master                    running (virtualbox)
$ vagrant halt
$ vagrant up --no-provision
Bringing machine 'node1' up with 'virtualbox' provider...
Bringing machine 'node2' up with 'virtualbox' provider...
Bringing machine 'master' up with 'virtualbox' provider...
==> node1: Checking if box 'centos/7' is up to date...
==> node1: Clearing any previously set forwarded ports...
==> node1: Clearing any previously set network interfaces...
==> node1: Preparing network interfaces based on configuration...
    node1: Adapter 1: nat
    node1: Adapter 2: hostonly
==> node1: Forwarding ports...
    node1: 22 (guest) => 2222 (host) (adapter 1)
==> node1: Running 'pre-boot' VM customizations...
==> node1: Booting VM...
==> node1: Waiting for machine to boot. This may take a few minutes...
    node1: SSH address: 127.0.0.1:2222
    node1: SSH username: vagrant
    node1: SSH auth method: private key
    node1: Warning: Remote connection disconnect. Retrying...
==> node1: Machine booted and ready!
==> node1: Checking for guest additions in VM...
    node1: No guest additions were detected on the base box for this VM! Guest
    node1: additions are required for forwarded ports, shared folders, host only
    node1: networking, and more. If SSH fails on this machine, please install
    node1: the guest additions and repackage the box to continue.
    node1:
    node1: This is not an error message; everything may continue to work properly,
    node1: in which case you may ignore this message.
==> node1: Setting hostname...
==> node1: Configuring and enabling network interfaces...
"""

And nothing…

Are there firewall or other think like this in VM that block ssh connection on port 2222 ?

Best regards,
Stéphane



--



--
Stéphane Klein <contact stephane-klein info>
blog: http://stephane-klein.info
cv : http://cv.stephane-klein.info
Twitter: http://twitter.com/klein_stephane

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]