[openstack-dev] [Neutron] Apparently weird timeout issue

Darragh O'Reilly dara2002-openstack at yahoo.com
Mon Jan 20 11:23:55 UTC 2014


Hi Salvatore,

I presume it's this one? 
http://logs.openstack.org/38/65838/4/check/check-tempest-dsvm-neutron-isolated/d108e4a/logs/tempest.txt.gz?#_2014-01-19_20_50_14_604

Is it true that the cirros image just fires off a few dhcp discovers and then gives up? If so, then maybe it did so before the tagging happened. Do we have the instance console log? It took about 45 seconds from when the port was created to when it was tagged.

2014-01-19 20:48:57.412 8142 DEBUG neutron.agent.linux.ovsdb_monitor [-] Output 
received from ovsdb monitor: 
{"data":[["3602a7b2-b559-4709-9bf0-53ae2af68d06","insert","tap496b808c-b5"]],"headings":["row","action","name"]}
<snip>
2014-01-19 20:49:41.925 8142 DEBUG neutron.agent.linux.utils [-] 
Command:
 ['sudo', '/usr/local/bin/neutron-rootwrap', 
'/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--timeout=10', 'set', 
'Port', 'tap496b808c-b5', 'tag=64']
Exit code: 0

Darragh.


>I have been seeing in the past 2 days timeout failures on gate jobs which I
>am struggling to explain. An example is available in [1]
>These are the usual failure that we associate with bug 1253896, but this
>time I can verify that:
>- The floating IP is correctly wired (IP and NAT rules)
>- The DHCP port is correctly wired, as well as the VM port and the router
>port
>- The DHCP agent is correctly started for the network
>
>However, no DHCP DISCOVER request is sent. Only the DHCP RELEASE message is
>seen.
>Any help at interpreting the logs will be appreciated.
>
>
>Salvatore
>
>[1] http://logs.openstack.org/38/65838
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140120/15409d81/attachment.html>


More information about the OpenStack-dev mailing list