VMs dont have connectivity in a 2 node deployment(Using GRE)

[Shweta P]

VMs instanciated in a multinode setup using GRE tunnels do not get an ip address. On running a tcpdump on the br-int on the compute nodes, I see a DHCP request being sent out, but no response received.

 Also the ovs-vsct show command does not show the peer ip(compute/control node ip) for with the bridge br-tun

root@control-server:~# ovs-vsctl show
7d231163-7c92-4c99-9a55-a1bf06aa8f21
    Bridge br-int
        Port "qr-19ed4da1-b5"
            tag: 1
            Interface "qr-19ed4da1-b5"
                type: internal
        Port "tap2edd8a14-62"
            tag: 1
            Interface "tap2edd8a14-62"
                type: internal
        Port br-int
            Interface br-int
                type: internal
    Bridge br-tun
        Port br-tun
            Interface br-tun
                type: internal
    Bridge br-ex
        Port "p4p2"
            Interface "p4p2"
        Port "qg-a627f1f2-49"
            Interface "qg-a627f1f2-49"
                type: internal
        Port br-ex
            Interface br-ex
                type: internal
    ovs_version: "2.0.1"

[Nikolay Fedotov (nfedotov)]

Here is /var/log/neutron folder content from my deployment

[Shannon McFarland (shmcfarl)]

I can confirm this. I see no endpoints for the GRE tunnels defined. The instances will never get an DHCP address. The puppet agent run and the various logs show nothing exciting related to GRE.

[Mark T. Voelker (mvoelker)]

I'm curious if those of you seeing this are actually getting your /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini files passed as --config-file arguments to the OVS agent and neutron server. There's a known bug with Ubuntu's packaging that may cause those files to be ignored or for ml2 config files to passed even if ml2 isn't being used. Do a "ps auwx|grep neutron" to see what --config-file arguments are being used. If you don't see ovs_neutron_plugin.ini in the list, restart the neutron server and ovs agent services manually, adding "--config-file /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" to the command line. Then retest and see if your GRE tunnels are set up properly.

[Mark T. Voelker (mvoelker)]

This patch should correct the config file issue...please test.

https://github.com/CiscoSystems/puppet-neutron/pull/3

[Tom Waterhouse (tomwater)]

Is this only for the 2_role scenario or for all? I would also like to test the change, but don't see that it is available in the puppet_openstack_builder project.

[cn (hichits)]

After adding /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini , GRE tunnel is getting created in the control node but it did not fix GRE tunnel in the compute node.

Here is the output from control note

root@bxbdl-c220-5:~# ovs-vsctl show
cf3f9710-aba1-42fa-85dc-fffa695dd890
    Bridge br-ex
        Port phy-br-ex
            Interface phy-br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "eth1"
            Interface "eth1"
    Bridge br-int
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port br-int
            Interface br-int
                type: internal
        Port int-br-ex
            Interface int-br-ex
    Bridge br-tun
        Port br-tun
            Interface br-tun
                type: internal
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port "gre-1"
            Interface "gre-1"
                type: gre
                options: {in_key=flow, local_ip="10.86.146.9", out_key=flow, remote_ip="10.86.146.11"}
    ovs_version: "2.0.2"
root@bxbdl-c220-5:~#

Here is the output from compute node.

root@bxbdl-c220-4:~# ovs-vsctl show
f99a4758-2251-4662-8f0e-05221eab76c9
    Bridge br-tun
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
    Bridge br-int
        Port int-br-ex
            Interface int-br-ex
        Port br-int
            Interface br-int
                type: internal
    Bridge br-ex
        Port phy-br-ex
            Interface phy-br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "eth1"
            Interface "eth1"
    ovs_version: "2.0.2"
root@bxbdl-c220-4:~#