Icehouse neutron can't access to instance with floating IP

asked 2014-06-11 06:08:12 -0500

Gyusik Hwang
21 ●1 ●1 ●5

updated 2014-06-11 19:10:06 -0500

Hi, All. I have deployed Openstack icehouse version on RHEL 6.5 for test lab followed by official guideline. After neutron configuration and initiate VM, I can't access to floating IP of VM. Nova instance have two interface for public and private network, I can't access neither of them. So, I can't reach instance. I have tried restart all things and re-configure neutron network. I'm not really familiar with openvswitch and networking, I have thought that i'm missing some important thing. Please help me.

I have two node configuration, first node act as controller, network node and compute node. and second node act as compute node.

Each node have two network interface, one for external and other for private.

**Controller Node and network node and compute node 1 (with External network IP -10.183.120.170)

[root@osnode01 neutron]# ifconfig -a
br-ex     Link encap:Ethernet  HWaddr 68:B5:99:C7:D2:8C  
          inet addr:10.183.120.170  Bcast:10.183.120.191  Mask:255.255.255.192
          inet6 addr: fe80::fc72:2dff:fe52:4709/64 Scope:Link
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:4698305 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4369482 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1803665841 (1.6 GiB)  TX bytes:1833241255 (1.7 GiB)

br-int    Link encap:Ethernet  HWaddr 8E:B9:63:DC:EE:45  
          inet6 addr: fe80::2c21:cff:fe90:d4fa/64 Scope:Link
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:536 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:32184 (31.4 KiB)  TX bytes:468 (468.0 b)

br-tun    Link encap:Ethernet  HWaddr D6:F1:17:0D:CA:4E  
          inet6 addr: fe80::8024:fdff:fe14:af81/64 Scope:Link
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:230 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:15164 (14.8 KiB)  TX bytes:468 (468.0 b)

eth0      Link encap:Ethernet  HWaddr 68:B5:99:C7:D2:8C  
          inet6 addr: fe80::6ab5:99ff:fec7:d28c/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:5101773 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4779571 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1851895406 (1.7 GiB)  TX bytes:1879660396 (1.7 GiB)

eth1      Link encap:Ethernet  HWaddr 68:B5:99:C7:D2:8E  
          inet addr:192.168.255.10  Bcast:192.168.255.255  Mask:255.255.255.0
          inet6 addr: fe80::6ab5:99ff:fec7:d28e/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:792 errors:0 dropped:0 overruns:0 frame:0
          TX packets:812 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 ...

(more)

edit retag flag offensive close merge delete

Comments

Please,
1. post ovs-vsctl show and ifconfig - on both nodes.
On Controller :-
2. neutron net-list
3. neutron router-list
4. ip netns

dbaxps ( 2014-06-11 06:48:21 -0500 )edit

I have updated content what you mentioned. ovs qr and qg interface LINK_DOWN status is normal behavior because of netns? I've tried to manually create namespace and ovs interface, but link may also change to down status right after move ovs interface to spcific namespace.

Gyusik Hwang ( 2014-06-11 19:24:35 -0500 )edit

Please, view link Router Interfaces Down . Your issues seem similar to described there.

dbaxps ( 2014-06-11 21:43:43 -0500 )edit

You also wrote : I've tried to manually create namespace and ovs interface, but link may also change to down status right after move ovs interface to spcific namespace. You are not supposed to do that.

dbaxps ( 2014-06-11 21:51:41 -0500 )edit

add a comment

answered 2014-06-12 00:38:22 -0500

Gyusik Hwang
21 ●1 ●1 ●5

updated 2014-06-12 00:41:47 -0500

Thanks for your answer. I found out that private IP is assigned to instance and can ssh instace with my user account (not root). Instance have two interface but only private interface is up. I tried to give public ip, but can't get root permission. I bulit suse image from susestudio with some root password, but i don't know why root password not works. maybe it's not an neutron problem,, I'm trying to find out any problem in nova or instance image.

edit flag offensive delete link

Comments

You should have a user account of particular tenant. If networks && router belong to this tenant ( or are in shared state), then you source your user/tenant credentials and attempt to issue floating IP for VM.
What are status qg-* && qr-* at your Controller ? Is this problem fixed ?

dbaxps ( 2014-06-12 01:25:25 -0500 )edit

I would also suggest trusty-server-cloudimg-amd64-disk1.img for testing VM deployment.

dbaxps ( 2014-06-12 01:31:24 -0500 )edit

I'm confused about using floating ip address. when I launch instance using gui, I just assigned private and public network interface at once. I'm sorry about my mistake. So, I launch instance with only private network interface, and then assign floating ip from external network. as a result, i can acess to vm from external network and vice versa. I can aware of my mistake using your ubuntu image. After assign floating ip to instance, i finally found that ip address assigned to interface and nat forwaring rule from qrouter namespace. Thanks for your help. :) And ovs-ofctl result still shows LINK_DOWN status.

Gyusik Hwang ( 2014-06-12 02:58:26 -0500 )edit

Please, confirm that problem with floating IP issue is gone as soon as
1. You use Ubuntu Cloud image from official site ( not mine ;)
2. You properly assign floating IP to Ubuntu cloud instance
what gives inbound && outbound Internet connectivity from within VM.

dbaxps ( 2014-06-12 04:14:33 -0500 )edit

add a comment

Icehouse neutron can't access to instance with floating IP

Comments

1 answer

Comments

Your Answer

Get to know Ask OpenStack

Question Tools

Stats

Related questions

Feedback About This Page

OpenStack

Community

Documentation

Branding & Legal

Icehouse neutron can't access to instance with floating IP edit

Comments

1 answer

Comments

Your Answer

Get to know Ask OpenStack

Question Tools

Stats

Related questions

Feedback About This Page

OpenStack

Community

Documentation

Branding & Legal

Icehouse neutron can't access to instance with floating IP