Chapter 3. Control Node in OpenStack Training Guides : Internet access lost after reboot

Bug #1292800 reported by Dan82
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Fix Released
Undecided
Pranav Salunke

Bug Description

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 the origin of the issue.

[UPDATE] I initiated another scratch install of the Control Node and I noticed the issue happens after modifying /etc/network/interfaces.
I modified this configuration file (See below) :
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 10.10.10.51
netmask 255.255.255.0

auto eth1
iface eth1 inet static
address 192.168.100.51
netmask 255.255.255.0

auto eth2
iface eth2 inet dhcp
gateway <IP address of my host machine>

It seems to work fine on ControlNode but I don't know real impact on other nodes (Compute and Network)

Regards
Dan
-----------------------------------
Built: 2014-02-01T02:08:38 00:00
git SHA: 6c21ae8135000d53704ca5ab21f9388a3f3c1b1e
URL: http://docs.openstack.org/training-guides/content/lab001-control-node.xml.html
source File: file:/home/jenkins/workspace/openstack-training-guides/doc/training-guides/lab001-control-node.xml
xml:id: lab001-control-node.xml

Dan82 (daniel-causse)
tags: added: configuration install virtualbox
Dan82 (daniel-causse)
description: updated
Dan82 (daniel-causse)
description: updated
Dan82 (daniel-causse)
tags: added: network
Dan82 (daniel-causse)
description: updated
Tom Fifield (fifieldt)
tags: added: training-guides
removed: configuration install network virtualbox
Changed in openstack-manuals:
assignee: nobody → Sean Roberts (sarob)
Revision history for this message
Anne Gentle (annegentle) wrote :

Sean, please triage.

Revision history for this message
Sean Roberts (sarob) wrote : Re: [Bug 1292800] Re: Chapter 3. Control Node in OpenStack Training Guides : Internet access lost after reboot

Will do thanks

~sean

> On Apr 7, 2014, at 7:26 AM, "Anne Gentle" <email address hidden> wrote:
>
> Sean, please triage.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1292800
>
> Title:
> Chapter 3. Control Node in OpenStack Training Guides : Internet access
> lost after reboot
>
> Status in OpenStack Manuals:
> New
>
> Bug description:
> 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 the origin of the issue.
>
> [UPDATE] I initiated another scratch install of the Control Node and I noticed the issue happens after modifying /etc/network/interfaces.
> I modified this configuration file (See below) :
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet static
> address 10.10.10.51
> netmask 255.255.255.0
>
> auto eth1
> iface eth1 inet static
> address 192.168.100.51
> netmask 255.255.255.0
>
> auto eth2
> iface eth2 inet dhcp
> gateway <IP address of my host machine>
>
> It seems to work fine on ControlNode but I don't know real impact on
> other nodes (Compute and Network)
>
> Regards
> Dan
> -----------------------------------
> Built: 2014-02-01T02:08:38 00:00
> git SHA: 6c21ae8135000d53704ca5ab21f9388a3f3c1b1e
> URL: http://docs.openstack.org/training-guides/content/lab001-control-node.xml.html
> source File: file:/home/jenkins/workspace/openstack-training-guides/doc/training-guides/lab001-control-node.xml
> xml:id: lab001-control-node.xml
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openstack-manuals/+bug/1292800/+subscriptions

Tom Fifield (fifieldt)
Changed in openstack-manuals:
milestone: none → juno
Revision history for this message
Pranav Salunke (dguitarbite) wrote :

It happens on some of the Laptops/Desktops which run on SATA disks/low hardware specs. It may be due to overhead of VirtualBox and/or issue inside the Virtual Machine. Let me take a look into this issue.

Can you post your Host's hardware configuration?

Changed in openstack-manuals:
assignee: Sean Roberts (sarob) → Pranav Salunke (dguitarbite)
status: New → Confirmed
Revision history for this message
Pranav Salunke (dguitarbite) wrote :

auto eth2
iface eth2 inet dhcp
gateway <IP address of my host machine>

This should not have gateway as it is obtained via. DHCP. This port is connected to NAT network of VirtualBox. It does not allow the instance to talk to your host machine, hence gateway as your host machine will result in loss of internet connection.

I need to put a few more lines on how to debug these issues happening in VirtualBox based installs. Thanks for reporting.

Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix proposed to openstack-manuals (master)

Fix proposed to branch: master
Review: https://review.openstack.org/90639

Changed in openstack-manuals:
status: Confirmed → In Progress
Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix merged to openstack-manuals (master)

Reviewed: https://review.openstack.org/90639
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=3750cff81b5f28ddb288b64f03c6e246bb1f7ad4
Submitter: Jenkins
Branch: master

commit 3750cff81b5f28ddb288b64f03c6e246bb1f7ad4
Author: Pranav Salunke <email address hidden>
Date: Mon Apr 28 10:14:06 2014 +0530

    Fixes Bug 1292800

    Added basic guidelines to follow for best results with VitrualBox
    for controller node.

    blueprint training-manuals
    Closes-Bug: #1292800

    Change-Id: I77165ff0d6e8b15ec09c14cd85d239097da5e032

Changed in openstack-manuals:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-manuals 15.0.0

This issue was fixed in the openstack/openstack-manuals 15.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.