> 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
Will do thanks
~sean
> On Apr 7, 2014, at 7:26 AM, "Anne Gentle" <email address hidden> wrote: /bugs.launchpad .net/bugs/ 1292800 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". interfaces file but I don't know if it's the origin of the issue. interfaces. ------- ------- ------- ------- 3704ca5ab21f938 8a3f3c1b1e docs.openstack. org/training- guides/ content/ lab001- control- node.xml. html jenkins/ workspace/ openstack- training- guides/ doc/training- guides/ lab001- control- node.xml control- node.xml /bugs.launchpad .net/openstack- manuals/ +bug/1292800/ +subscriptions
>
> Sean, please triage.
>
> --
> You received this bug notification because you are a bug assignee.
> https:/
>
> 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/
> - 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/
>
> [UPDATE] I initiated another scratch install of the Control Node and I noticed the issue happens after modifying /etc/network/
> 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: 6c21ae8135000d5
> URL: http://
> source File: file:/home/
> xml:id: lab001-
>
> To manage notifications about this bug go to:
> https:/