Mailing List Archive

Networking Issue (of newly launched instance)
Hi All,

I have been able to launch an instance using devstack's dashboard. Now there seems to be networking problem. The log of the launched instance shows the following message repeatedly:

cloud-setup: failed 1/30 : up 1.23. request failed
wget: can't connect to remote host (169.254.169.254): No route to host

and afterwards, the log shows:
############ debug start ##############
### /etc/rc.d/init.d/sshd start
/etc/rc3.d/S45-cloud-setup: line 66: /etc/rc.d/init.d/sshd: not found
### ifconfig -a
eth0 Link encap:Ethernet HWaddr FA:16:3E:28:AB:91
inet addr:10.0.3.19 Bcast:10.0.3.255 Mask:255.255.255.0
inet6 addr: fe80::f816:3eff:fe28:ab91/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:96 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3054 (2.9 KiB) TX bytes:4780 (4.6 KiB)
Interrupt:11 Base address:0xa000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4928 (4.8 KiB) TX bytes:4928 (4.8 KiB)

### route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.0.3.2 0.0.0.0 UG 0 0 0 eth0
10.0.3.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
### cat /etc/resolv.conf
search hsd1.il.comcast.net.
nameserver 192.168.1.1
### ping -c 5 10.0.3.2
PING 10.0.3.2 (10.0.3.2): 56 data bytes

--- 10.0.3.2 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

### pinging nameservers
#### ping -c 5 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
and after sometime:
wget: can't connect to remote host (169.254.169.254): No route to host
instance-id:
public-ipv4:
local-ipv4 :
wget: can't connect to remote host (169.254.169.254): No route to host
cloud-userdata: failed to read instance id
WARN: /etc/rc3.d/S99-cloud-userdata failed

Although the dashboard shows an IP of 10.0.0.3 for this instance, yet within the logs ifconfig -a is showing 10.0.3.19. I am not sure how this instance is connected to my host (or how it should be connected to my host). Someone help please, I can not even login to the instance using VNC. (Any insights to the networking part would be really helpful)

This is my setup:
My host VM (which is hosting devstack) has two VNICs: eth0 is NAT (IP:10.0.3.15) and eth1 is host only (IP:192.168.124.2). All devstack's configuration has been done with respect to 10.0.3.15 (i.e all services are bound to this address)
Re: Networking Issue (of newly launched instance) [ In reply to ]

I think the dhcp message is intercepted by your host's dhcp server.

-----openstack-bounces+gongysh=cn.ibm.com@lists.launchpad.net wrote: -----

To: <openstack@lists.launchpad.net>
From: Salman Malik <salmanmk@live.com>
Sent by: openstack-bounces+gongysh=cn.ibm.com@lists.launchpad.net
Date: 04/16/2012 12:30AM
Subject: [Openstack] Networking Issue (of newly launched instance)

Hi All,

I have been able to launch an instance using devstack's dashboard. Now there seems to be networking problem. The log of the launched instance shows the following message repeatedly:

cloud-setup: failed 1/30 : up 1.23. request failed
wget: can't connect to remote host (169.254.169.254): No route to host

and afterwards, the log shows:
############ debug start ##############
### /etc/rc.d/init.d/sshd start
/etc/rc3.d/S45-cloud-setup: line 66: /etc/rc.d/init.d/sshd: not found
### ifconfig -a
eth0 Link encap:Ethernet HWaddr FA:16:3E:28:AB:91
inet addr:10.0.3.19 Bcast:10.0.3.255 Mask:255.255.255.0
inet6 addr: fe80::f816:3eff:fe28:ab91/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:96 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3054 (2.9 KiB) TX bytes:4780 (4.6 KiB)
Interrupt:11 Base address:0xa000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4928 (4.8 KiB) TX bytes:4928 (4.8 KiB)

### route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.0.3.2 0.0.0.0 UG 0 0 0 eth0
10.0.3.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
### cat /etc/resolv.conf
search hsd1.il.comcast.net.
nameserver 192.168.1.1
### ping -c 5 10.0.3.2
PING 10.0.3.2 (10.0.3.2): 56 data bytes

--- 10.0.3.2 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

### pinging nameservers
#### ping -c 5 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
and after sometime:
wget: can't connect to remote host (169.254.169.254): No route to host
instance-id:
public-ipv4:
local-ipv4 :
wget: can't connect to remote host (169.254.169.254): No route to host
cloud-userdata: failed to read instance id
WARN: /etc/rc3.d/S99-cloud-userdata failed


Although the dashboard shows an IP of 10.0.0.3 for this instance, yet within the logs ifconfig -a is showing 10.0.3.19. I am not sure how this instance is connected to my host (or how it should be connected to my host). Someone help please, I can not even login to the instance using VNC. (Any insights to the networking part would be really helpful)

This is my setup:
My host VM (which is hosting devstack) has two VNICs: eth0 is NAT (IP:10.0.3.15) and eth1 is host only (IP:192.168.124.2). All devstack's configuration has been done with respect to 10.0.3.15 (i.e all services are bound to this address)
_______________________________________________
Mailing list: https://launchpad.net/%7Eopenstack"]https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/%7Eopenstack"]https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp"]https://help.launchpad.net/ListHelp

Re: Networking Issue (of newly launched instance) [ In reply to ]
Thanks Sheng. I think you are right. But how to resolve the issue ?

Subject: Re: [Openstack] Networking Issue (of newly launched instance)
From: gongysh@cn.ibm.com
To: salmanmk@live.com
CC: openstack@lists.launchpad.net
Date: Mon, 16 Apr 2012 07:47:17 +0800


I think the dhcp message is intercepted by your host's dhcp server.

-----openstack-bounces+gongysh=cn.ibm.com@lists.launchpad.net wrote: -----

To: <openstack@lists.launchpad.net>
From: Salman Malik <salmanmk@live.com>
Sent by: openstack-bounces+gongysh=cn.ibm.com@lists.launchpad.net
Date: 04/16/2012 12:30AM
Subject: [Openstack] Networking Issue (of newly launched instance)







Hi All,

I have been able to launch an instance using devstack's dashboard. Now there seems to be networking problem. The log of the launched instance shows the following message repeatedly:

cloud-setup: failed 1/30 : up 1.23. request failed
wget: can't connect to remote host (169.254.169.254): No route to host

and afterwards, the log shows:
############ debug start ##############
### /etc/rc.d/init.d/sshd start
/etc/rc3.d/S45-cloud-setup: line 66: /etc/rc.d/init.d/sshd: not found
### ifconfig -a
eth0 Link encap:Ethernet HWaddr FA:16:3E:28:AB:91
inet addr:10.0.3.19 Bcast:10.0.3.255 Mask:255.255.255.0
inet6 addr: fe80::f816:3eff:fe28:ab91/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:96 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3054 (2.9 KiB) TX bytes:4780 (4.6 KiB)
Interrupt:11 Base address:0xa000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4928 (4.8 KiB) TX bytes:4928 (4.8 KiB)

### route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.0.3.2 0.0.0.0 UG 0 0 0 eth0
10.0.3.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
### cat /etc/resolv.conf
search hsd1.il.comcast.net.
nameserver 192.168.1.1
### ping -c 5 10.0.3.2
PING 10.0.3.2 (10.0.3.2): 56 data bytes

--- 10.0.3.2 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

### pinging nameservers
#### ping -c 5 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
and after sometime:
wget: can't connect to remote host (169.254.169.254): No route to host
instance-id:
public-ipv4:
local-ipv4 :
wget: can't connect to remote host (169.254.169.254): No route to host
cloud-userdata: failed to read instance id
WARN: /etc/rc3.d/S99-cloud-userdata failed

Although the dashboard shows an IP of 10.0.0.3 for this instance, yet within the logs ifconfig -a is showing 10.0.3.19. I am not sure how this instance is connected to my host (or how it should be connected to my host). Someone help please, I can not even login to the instance using VNC. (Any insights to the networking part would be really helpful)

This is my setup:
My host VM (which is hosting devstack) has two VNICs: eth0 is NAT (IP:10.0.3.15) and eth1 is host only (IP:192.168.124.2). All devstack's configuration has been done with respect to 10.0.3.15 (i.e all services are bound to this address)

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: Networking Issue (of newly launched instance) [ In reply to ]
I remember that in one of companies that I have worked for, any employees are prohibited to run a DHCP server attached to office network.

Seems you have to find a way to isolate your host dhcp server with your nova-network dhcp server if you have to run both servers.

-----Salman Malik <salmanmk@live.com> wrote: -----

To: Yong Sheng Gong/China/IBM@IBMCN
From: Salman Malik <salmanmk@live.com>
Date: 04/16/2012 07:55AM
Cc: <openstack@lists.launchpad.net>
Subject: RE: [Openstack] Networking Issue (of newly launched instance)

Thanks Sheng. I think you are right. But how to resolve the issue ?


Subject: Re: [Openstack] Networking Issue (of newly launched instance)
From: gongysh@cn.ibm.com
To: salmanmk@live.com
CC: openstack@lists.launchpad.net
Date: Mon, 16 Apr 2012 07:47:17 +0800


I think the dhcp message is intercepted by your host's dhcp server.

-----openstack-bounces+gongysh=cn.ibm.com@lists.launchpad.net wrote: -----

To: <openstack@lists.launchpad.net>
From: Salman Malik <salmanmk@live.com>
Sent by: openstack-bounces+gongysh=cn.ibm.com@lists.launchpad.net
Date: 04/16/2012 12:30AM
Subject: [Openstack] Networking Issue (of newly launched instance)

Hi All,

I have been able to launch an instance using devstack's dashboard. Now there seems to be networking problem. The log of the launched instance shows the following message repeatedly:

cloud-setup: failed 1/30 : up 1.23. request failed
wget: can't connect to remote host (169.254.169.254): No route to host

and afterwards, the log shows:
############ debug start ##############
### /etc/rc.d/init.d/sshd start
/etc/rc3.d/S45-cloud-setup: line 66: /etc/rc.d/init.d/sshd: not found
### ifconfig -a
eth0 Link encap:Ethernet HWaddr FA:16:3E:28:AB:91
inet addr:10.0.3.19 Bcast:10.0.3.255 Mask:255.255.255.0
inet6 addr: fe80::f816:3eff:fe28:ab91/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:96 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3054 (2.9 KiB) TX bytes:4780 (4.6 KiB)
Interrupt:11 Base address:0xa000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4928 (4.8 KiB) TX bytes:4928 (4.8 KiB)

### route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.0.3.2 0.0.0.0 UG 0 0 0 eth0
10.0.3.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
### cat /etc/resolv.conf
search hsd1.il.comcast.net.
nameserver 192.168.1.1
### ping -c 5 10.0.3.2
PING 10.0.3.2 (10.0.3.2): 56 data bytes

--- 10.0.3.2 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

### pinging nameservers
#### ping -c 5 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
and after sometime:
wget: can't connect to remote host (169.254.169.254): No route to host
instance-id:
public-ipv4:
local-ipv4 :
wget: can't connect to remote host (169.254.169.254): No route to host
cloud-userdata: failed to read instance id
WARN: /etc/rc3.d/S99-cloud-userdata failed


Although the dashboard shows an IP of 10.0.0.3 for this instance, yet within the logs ifconfig -a is showing 10.0.3.19. I am not sure how this instance is connected to my host (or how it should be connected to my host). Someone help please, I can not even login to the instance using VNC. (Any insights to the networking part would be really helpful)

This is my setup:
My host VM (which is hosting devstack) has two VNICs: eth0 is NAT (IP:10.0.3.15) and eth1 is host only (IP:192.168.124.2). All devstack's configuration has been done with respect to 10.0.3.15 (i.e all services are bound to this address)
_______________________________________________
Mailing list: https://launchpad.net/%7Eopenstack"]https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/%7Eopenstack"]https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp"]https://help.launchpad.net/ListHelp



Re: Networking Issue (of newly launched instance) [ In reply to ]
Hi there !

On 04/15/2012 06:30 PM, Salman Malik wrote:
> Hi All,
>
> I have been able to launch an instance using devstack's dashboard. Now
> there seems to be networking problem. The log of the launched instance
> shows the following message repeatedly:
>
> cloud-setup: failed 1/30 : up 1.23. request failed
> wget: can't connect to remote host (169.254.169.254): No route to host
>
> and afterwards, the log shows:

169.254.169.254 is the ip of whatever serves the "metadata" ubuntu
instances needs after the boot (to get the ssh key).

I had such"cant connect to 169.254.169.254) on some compute-node where
nova-api was not running:

http://docs.openstack.org/cactus/openstack-compute/admin/content/configuring-multiple-compute-nodes.html

Note sure it apply on your case as you mention devstack (so i am
assuming you are using only 1 node), but it could be worth checking that
nova-api is actually running.


_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp