<div dir="ltr"><div>Guys,</div><div><br></div><div>I trying to enable the GRE tunnels in my Havana environment but, I'm seeing the following error messages at my Controller Node, after restarting `neutron-plugin-openvswitch-agent`:</div>
<div><br></div><div>---</div><div>==> /var/log/neutron/openvswitch-agent.log <==</div><div>2013-10-21 06:01:24.204 6575 INFO neutron.common.config [-] Logging enabled!</div><div>2013-10-21 06:01:24.273 6575 INFO neutron.openstack.common.rpc.common [-] Connected to AMQP server on <a href="http://controller-1.yourdomain.com:5672">controller-1.yourdomain.com:5672</a></div>
<div>2013-10-21 06:01:24.320 6575 INFO neutron.openstack.common.rpc.common [-] Connected to AMQP server on <a href="http://controller-1.yourdomain.com:5672">controller-1.yourdomain.com:5672</a></div><div><br></div><div>==> /var/log/openvswitch/ovs-vswitchd.log <==</div>
<div>2013-10-21T08:01:24Z|00061|bridge|INFO|bridge br-tun: added interface br-tun on port 65534</div><div>2013-10-21T08:01:24Z|00062|bridge|INFO|bridge br-tun: using datapath ID 000002fd0fd7f945</div><div>2013-10-21T08:01:24Z|00063|connmgr|INFO|br-tun: added service controller "punix:/var/run/openvswitch/br-tun.mgmt"</div>
<div>2013-10-21T08:01:24Z|00064|netdev_linux|WARN|ethtool command ETHTOOL_GFLAGS on network device patch-tun failed: No such device</div><div>2013-10-21T08:01:24Z|00065|dpif|WARN|system@ovs-system: failed to add patch-tun as port: No such device</div>
<div>2013-10-21T08:01:24Z|00066|netdev_vport|ERR|patch-tun: patch type requires valid 'peer' argument</div><div>2013-10-21T08:01:24Z|00067|bridge|WARN|could not configure network device patch-tun (Invalid argument)</div>
<div>2013-10-21T08:01:24Z|00068|bridge|INFO|bridge br-int: added interface patch-tun on port 3</div><div>2013-10-21T08:01:24Z|00069|netdev_linux|WARN|ethtool command ETHTOOL_GFLAGS on network device patch-int failed: No such device</div>
<div>2013-10-21T08:01:24Z|00070|dpif|WARN|system@ovs-system: failed to add patch-int as port: No such device</div><div>2013-10-21T08:01:24Z|00071|netdev_vport|ERR|patch-int: patch type requires valid 'peer' argument</div>
<div>2013-10-21T08:01:24Z|00072|bridge|WARN|could not configure network device patch-int (Invalid argument)</div><div>2013-10-21T08:01:24Z|00073|bridge|INFO|bridge br-tun: added interface patch-int on port 1</div><div><br>
</div><div>==> /var/log/neutron/openvswitch-agent.log <==</div><div>2013-10-21 06:01:25.702 6575 INFO neutron.plugins.openvswitch.agent.ovs_neutron_agent [-] Agent initialized successfully, now running...</div><div>
2013-10-21 06:01:25.702 6575 INFO neutron.plugins.openvswitch.agent.ovs_neutron_agent [-] Agent out of sync with plugin!</div><div>2013-10-21 06:01:25.703 6575 INFO neutron.plugins.openvswitch.agent.ovs_neutron_agent [-] Agent tunnel out of sync with plugin!</div>
<div>2013-10-21 06:01:25.716 6575 INFO neutron.openstack.common.rpc.common [-] Connected to AMQP server on <a href="http://controller-1.yourdomain.com:5672">controller-1.yourdomain.com:5672</a></div><div><br></div><div>==> /var/log/openvswitch/ovs-vswitchd.log <==</div>
<div>2013-10-21T08:01:25Z|00074|netdev_linux|WARN|ethtool command ETHTOOL_GFLAGS on network device gre-2 failed: No such device</div><div>2013-10-21T08:01:25Z|00075|dpif|WARN|system@ovs-system: failed to add gre-2 as port: No such device</div>
<div>2013-10-21T08:01:25Z|00076|netdev_vport|ERR|gre-2: gre type requires valid 'remote_ip' argument</div><div>2013-10-21T08:01:25Z|00077|bridge|WARN|could not configure network device gre-2 (Invalid argument)</div>
<div>2013-10-21T08:01:25Z|00078|bridge|INFO|bridge br-tun: added interface gre-2 on port 2</div><div>---</div><div><br></div><div>I'm following the same topology described here:</div><div><br></div><div><a href="https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst">https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst</a></div>
<div><br></div><div>But, of course, make the changes to reflect Havana needs, as package names and etc...</div><div><br></div><div>My Instances doesn't get an IP from the DHCP. I'm running the command `tcpdump -ni eth1` at my Network Node (interface used by OVS for the GRE tunnel) and I'm seeing the DHCP requests coming into the Network Node but, it does not reach DHCP server within the tenant namespace...</div>
<div><br></div><div>I mean, from the inside of tenant's "qdhcp-*" Namespace, there is no DHCP requests hitting it.</div><div><br></div><div>Apparently, the GRE tunnel is UP, since at the Network Node, I can see the DHCP requests coming from the Intances but, they never hit the tenant DHCP server within its own Namespace...</div>
<div><br></div><div>I already tried to start again from scratch, this error messages appear before creating new Networks and Subnets with Neutron. Later, the Instances doesn't get an IP...</div><div><br></div><div>I'm using Ubuntu 12.04.3 - Linux 3.8 - OVS 1.10.2 from Havana Cloud Archive.</div>
<div><br></div><div>Any tips?!</div><div><br></div><div>Thanks!</div><div>Thiago</div></div>