<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 29 Jan 2014, at 17:12, George Shuklin <<a href="mailto:george.shuklin@gmail.com">george.shuklin@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Very annoying situation, every time it
really hard to debug.<br>
<br>
My debug experience so far:<br>
<br>
Easy:<br>
1. Check every /var/log/upstart/neutron*.log file. Sometime stupid
typo in configs cause problems.<br>
2. Check access group for instance.<br>
<br>
In depth:<br>
Check ovs-ofctl dump-flows br-tun on compute where instance is
running. Proper configuration should contain lines like this:<br>
<br>
cookie=0x0, duration=216.991s, table=21, n_packets=19,
n_bytes=2326, idle_age=144, priority=1,dl_vlan=3
actions=strip_vlan,set_tunnel:0x1,output:6,output:5,output:2,output:3,output:4<br>
(table=21, and set_tunnel, output - is important).<br>
<br>
I create a very crude utility to probing gre tunnels:
<a class="moz-txt-link-freetext" href="https://github.com/amarao/gre-tun-probe">https://github.com/amarao/gre-tun-probe</a> to check if everything is
fine.<br>
<br>
One more hint: Ubuntu cut off neutron-ovs-cleanup script. Run it
and reboot compute node, may be it will helps.<br>
<br></div></div></blockquote><div><br></div><div>Hi, thank you for your answer. I see that I’re assuming I’m using gee, aren’t you ?</div><div><br></div><div>I’ve setup everything for [local] on SL 6.4 platform.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Alvise</div><br><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000"><div class="moz-cite-prefix">
<br>
On 29.01.2014 17:25, Alvise Dorigo wrote:<br>
</div>
<blockquote cite="mid:983C40A2-B1C8-4918-83E2-AB099A95F507@pd.infn.it" type="cite">
<div>Hello,</div>
<div>I've a distributed installation of OpenStack Havana on 3
different nodes:</div>
<div><br>
</div>
<div> 1. Controller node: nova-api + nova-cert + nova-scheduler +
nova-consoleauth + nova-novncproxy + nova-conductor + keystone +
glance + neutron server + Dashboard</div>
<div><br>
</div>
<div> 2. compute node: nova-compute</div>
<div><br>
</div>
<div> 3. network node: l3-agent + dhcp-agent + metadata-agent</div>
<div><br>
</div>
<div>Of course, on all of them, the l2-agent
(neutron-openvswitch-agent) is also running.</div>
<div><br>
</div>
<div>From the dashboard I created a simple cirros image; then I
launched it and attached to an non-external network (created in
the Admin project, and having its own subnet and dhcp enabled).
Nova assigned an IP to the VM, but actually when the VM's
operating system bootstrapped it couldn't obtain from the DHCP
the assigned IP.</div>
<div><br>
</div>
<div>I monitored the br-int interface on the compute node and on
the network node, using "tcpdump -i br-int".</div>
<div><br>
</div>
<div>I saw the packet traffic going through the two br-int
interfaces (from compute node to network node). But when I
monitored the tapXYZ... in the dhcp network namespace (in the
network node) I didn't see any packet traversing it:</div>
<div><br>
</div>
<div> ip netns exec qdhcpXYZ… "tcpdump -i tap37fgw74frwgc"</div>
<div><br>
</div>
<div>… nothing … :-(</div>
<div><br>
</div>
<div>So, it seems that the DHCP client's request correctly
originates from the VM, and is correctly trasmitted to the
network node by mean of the data network the two br-int
interfaces are connected to; but for some reason the dhcp-agent
doesn't receive anything, as proved by the null traffic on its
tap.</div>
<div><br>
</div>
<div>Any idea about what and how I could more deeply investigate ?</div>
<div><br>
</div>
<div>thanks,</div>
<div>Alvise</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-operators mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>OpenStack-operators mailing list<br><a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators<br></blockquote></div><br></body></html>