Never mind... After adding:
dhcp-option-force=26,1400 to: /etc/neutron/dnsmasq-neutron.conf My setup is working... Anyway, there are still errors on my logs but, I'm ignoring it, since my cloud seems to be working okay now... :-/ Tks! Thiago On 21 October 2013 06:15, Martinx - ジェームズ <[email protected]> wrote: > Guys, > > 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`: > > --- > ==> /var/log/neutron/openvswitch-agent.log <== > 2013-10-21 06:01:24.204 6575 INFO neutron.common.config [-] Logging > enabled! > 2013-10-21 06:01:24.273 6575 INFO neutron.openstack.common.rpc.common [-] > Connected to AMQP server on controller-1.yourdomain.com:5672 > 2013-10-21 06:01:24.320 6575 INFO neutron.openstack.common.rpc.common [-] > Connected to AMQP server on controller-1.yourdomain.com:5672 > > ==> /var/log/openvswitch/ovs-vswitchd.log <== > 2013-10-21T08:01:24Z|00061|bridge|INFO|bridge br-tun: added interface > br-tun on port 65534 > 2013-10-21T08:01:24Z|00062|bridge|INFO|bridge br-tun: using datapath ID > 000002fd0fd7f945 > 2013-10-21T08:01:24Z|00063|connmgr|INFO|br-tun: added service controller > "punix:/var/run/openvswitch/br-tun.mgmt" > 2013-10-21T08:01:24Z|00064|netdev_linux|WARN|ethtool command > ETHTOOL_GFLAGS on network device patch-tun failed: No such device > 2013-10-21T08:01:24Z|00065|dpif|WARN|system@ovs-system: failed to add > patch-tun as port: No such device > 2013-10-21T08:01:24Z|00066|netdev_vport|ERR|patch-tun: patch type requires > valid 'peer' argument > 2013-10-21T08:01:24Z|00067|bridge|WARN|could not configure network device > patch-tun (Invalid argument) > 2013-10-21T08:01:24Z|00068|bridge|INFO|bridge br-int: added interface > patch-tun on port 3 > 2013-10-21T08:01:24Z|00069|netdev_linux|WARN|ethtool command > ETHTOOL_GFLAGS on network device patch-int failed: No such device > 2013-10-21T08:01:24Z|00070|dpif|WARN|system@ovs-system: failed to add > patch-int as port: No such device > 2013-10-21T08:01:24Z|00071|netdev_vport|ERR|patch-int: patch type requires > valid 'peer' argument > 2013-10-21T08:01:24Z|00072|bridge|WARN|could not configure network device > patch-int (Invalid argument) > 2013-10-21T08:01:24Z|00073|bridge|INFO|bridge br-tun: added interface > patch-int on port 1 > > ==> /var/log/neutron/openvswitch-agent.log <== > 2013-10-21 06:01:25.702 6575 INFO > neutron.plugins.openvswitch.agent.ovs_neutron_agent [-] Agent initialized > successfully, now running... > 2013-10-21 06:01:25.702 6575 INFO > neutron.plugins.openvswitch.agent.ovs_neutron_agent [-] Agent out of sync > with plugin! > 2013-10-21 06:01:25.703 6575 INFO > neutron.plugins.openvswitch.agent.ovs_neutron_agent [-] Agent tunnel out of > sync with plugin! > 2013-10-21 06:01:25.716 6575 INFO neutron.openstack.common.rpc.common [-] > Connected to AMQP server on controller-1.yourdomain.com:5672 > > ==> /var/log/openvswitch/ovs-vswitchd.log <== > 2013-10-21T08:01:25Z|00074|netdev_linux|WARN|ethtool command > ETHTOOL_GFLAGS on network device gre-2 failed: No such device > 2013-10-21T08:01:25Z|00075|dpif|WARN|system@ovs-system: failed to add > gre-2 as port: No such device > 2013-10-21T08:01:25Z|00076|netdev_vport|ERR|gre-2: gre type requires valid > 'remote_ip' argument > 2013-10-21T08:01:25Z|00077|bridge|WARN|could not configure network device > gre-2 (Invalid argument) > 2013-10-21T08:01:25Z|00078|bridge|INFO|bridge br-tun: added interface > gre-2 on port 2 > --- > > I'm following the same topology described here: > > > https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst > > But, of course, make the changes to reflect Havana needs, as package names > and etc... > > 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... > > I mean, from the inside of tenant's "qdhcp-*" Namespace, there is no DHCP > requests hitting it. > > 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... > > 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... > > I'm using Ubuntu 12.04.3 - Linux 3.8 - OVS 1.10.2 from Havana Cloud > Archive. > > Any tips?! > > Thanks! > Thiago >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
