[FIXED] Network issue after VM reboot

[Dan82]

Hello,

I installed OpenStack in a VirtualBox 4.3.8 environment following instructions from http://docs.openstack.org/training-guid ... e.xml.html. The issue is about Control Node virtual machine. I installed Ubuntu 12.04 Server LTE on the virtual machine then I installed all OpenStack services.

At the end of installation, everything looked OK (ping to external sites worked fine) so I made a snapshot of Control Node configuration.

The issue happens when I reboot the Control Node virtual machine, all ping instructions to external domains (or IP addresses, including host machine) generate unknown host message.

I performed only the two following actions between install and reboot:
- Adding line "ServerName ControlNode" in /etc/apache2/httpd.conf file in order to avoid message "Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName".
- apt-get install --reinstall iscsitarget-dkms due to message "iscsi-target fatal module iscsi_trgt not found"

During startup, all services are [OK], I just have messages:
Waiting for network configuration
Waiting an additional 60 seconds for network configuration
Booting system without full network configuration
I read this message was due to existence of 2 gateways in /etc/network/interfaces file but I don't know if it's a severe issue.

/etc/network/interfaces content (comments removed) :

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 10.10.10.51
netmask 255.255.255.0
gateway 10.10.10.1

auto eth1
iface eth1 inet static
address 192.168.100.51
netmask 255.255.255.0
gateway 192.168.100.1

auto eth2
iface eth2 inet dhcp

/etc/hosts content:
127.0.0.1 localhost
127.0.1.1 ControlNode
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

/etc/resolv.conf content:
nameserver 80.10.246.2
nameserver 80.10.246.3

I tested several corrections in network files but they didn't resolve my issue. Help would be appreciated.

Regards Dan

[Perryg]

Looks like a configuration issue from within the guest. I don't like doubling up on gateways as it will cause the network to fail since it does not know where to actually look.
I believe you will need to ask the person responsible for your tutorial what you need to do.

[Dan82]

Hello Perryg,

I initiated another scratch install and I noticed the issue happens after modifying /etc/network/interfaces; the issue is fixed if I remove gateway 10.10.10.1 line.

I'm currently waiting for a reply from the author of the tutorial in order to update and close this thread.

Regards
Dan

[Perryg]

Ok, but you might as well close it now, as it is not an issue with VirtualBox. All VBox does is simulate hardware, and if it works with one GW it works.

[Dan82]

Hello,

I confirm issue was due to /etc/network/interfaces misconfiguration, so this thread can be closed.

PS : Where is the "Close" button?

Regards
Dan