neutron

Floating IPs seem disconnected

Asked by Joshua Dotson

Hi,

I followed this guide and other multi-node GRE guides: https://github.com/josh-wrale/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst

I'm on 12.10 with three nodes.. Control, network and compute. I have L3_agent and DHCP agent running on network node. Namespaces are enabled. My VM's can get a private DHCP address. However, when I create and associate a floating IP, it never seems to actually work.

I'm getting frustrated with the ERROR: No public addresses found for 'VM_NAME' response from nova ssh from an external host.

When I associate a floating IP with a VM, shouldn't nova list show the private IP, as well as the public IP? My VM's show no other IP than the primary private IP. And the floating IP isn't pingable from the general public network.

Dump of background info:

http://pastebin.com/raw.php?i=a7VgKFEa

Thanks,
Joshua

Question information

Language:
English Edit question
Status:
Solved
For:
neutron Edit question
Assignee:
No assignee Edit question
Solved by:
Joshua Dotson
Solved:
Last query:
Last reply:
Revision history for this message
dan wendlandt (danwent) said : 		#1

thanks for the detailed report. this looks like a bug, as you should see the floating IPs as additional ips on the interface qg-a62da873-41 in the following output in you log:

root@knet-hj29:/var/log/quantum# ip netns exec qrouter-6e6f6f2d-45bd-40c1-b877-38df17c7394c ifconfig
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:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:672 (672.0 B) TX bytes:672 (672.0 B)

qg-a62da873-41 Link encap:Ethernet HWaddr fa:16:3e:c1:44:a9
          inet addr:192.168.10.151 Bcast:192.168.10.255 Mask:255.255.255.0
          inet6 addr: fe80::f816:3eff:fec1:44a9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:15243 errors:0 dropped:0 overruns:0 frame:0
          TX packets:759 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2261925 (2.2 MB) TX bytes:65187 (65.1 KB)

qr-b0755118-69 Link encap:Ethernet HWaddr fa:16:3e:86:47:f3
          inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0
          inet6 addr: fe80::f816:3eff:fe86:47f3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:695 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2692 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:75616 (75.6 KB) TX bytes:268972 (268.9 KB)

Can you see if there are errors in the log for the quantum-l3-agent?

Revision history for this message
Joshua Dotson (tns9) said : 		#2

Here's what I see after doing a cat '' > /var/log/l3_agent.log, then a reboot.

root@knet-hj29:/var/log/quantum# ip netns exec qrouter-6e6f6f2d-45bd-40c1-b877-38df17c7394c ifconfig
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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

qg-a62da873-41 Link encap:Ethernet HWaddr fa:16:3e:c1:44:a9
          inet addr:192.168.10.151 Bcast:192.168.10.255 Mask:255.255.255.0
          inet6 addr: fe80::f816:3eff:fec1:44a9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:96 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:14054 (14.0 KB) TX bytes:822 (822.0 B)

qr-b0755118-69 Link encap:Ethernet HWaddr fa:16:3e:86:47:f3
          inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0
          inet6 addr: fe80::f816:3eff:fe86:47f3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:19 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2574 (2.5 KB) TX bytes:1296 (1.2 KB)

root@knet-hj29:/var/log/quantum# wc -l l3-agent.log
1821 l3-agent.log
root@knet-hj29:/var/log/quantum# grep -i error l3-agent.log
2012-12-18 00:37:11 ERROR [quantum.agent.l3_agent] external network bridge 'br-ex' does not exist
root@knet-hj29:/var/log/quantum# brctl show
bridge name bridge id STP enabled interfaces
br-ex 0000.001018c8b008 no eth2
       qg-a62da873-41
br-int 0000.2e7f5adc704a no qr-b0755118-69
       tap74aa47b1-9d
br-tun 0000.fa56c1c7f44f no
root@knet-hj29:/var/log/quantum# ovs-vsctl show
d13dabe6-eaaf-4244-92a6-1bd9ce0def35
    Bridge br-tun
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port "gre-2"
            Interface "gre-2"
                type: gre
                options: {in_key=flow, out_key=flow, remote_ip="172.20.10.53"}
        Port br-tun
            Interface br-tun
                type: internal
    Bridge br-int
        Port br-int
            Interface br-int
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "tap74aa47b1-9d"
            tag: 1
            Interface "tap74aa47b1-9d"
                type: internal
        Port "qr-b0755118-69"
            tag: 1
            Interface "qr-b0755118-69"
                type: internal
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "qg-a62da873-41"
            Interface "qg-a62da873-41"
                type: internal
        Port "eth2"
            Interface "eth2"
    ovs_version: "1.4.3"
root@knet-hj29:/var/log/quantum#

Revision history for this message
Joshua Dotson (tns9) said : 		#3

I think I'm going to rebuild...again.. This time, I'll try the new guide which was announced/revised(?) today: http://docs.openstack.org/folsom/basic-install/content/

I've built my test environment in about ten different ways over the past month or two. At the end of every single one, I've run into problems. I suppose I could throw in the towel and retreat to nova-network and Essex, but I'd really rather just figure out what I'm doing wrong.

Thanks for the help. Here's to another failed install. lol

-Joshua