Public bug reported: I couldn't find obvious existing bugs with the same failures so reporting a new one. This is a nova compute test that fails but it's failing because neutron isn't serving a port for the instance.
The nova compute errors are pretty obvious but doesn't give a good reason why it fails: http://logs.openstack.org/25/64725/4/check/check-tempest-dsvm- neutron/811ce6f/logs/screen-n-cpu.txt.gz?level=TRACE The neutron server logs are full of errors, so I'm not sure which is the root cause: http://logs.openstack.org/25/64725/4/check/check-tempest-dsvm- neutron/811ce6f/logs/screen-q-svc.txt.gz?level=TRACE Looks like neutron is just dead or in terrible shape for some reason. I'm actually surprised there aren't more test failures in this run given all of the errors in the neutron logs. The errors are more limited in the dhcp agent logs, looks like a problem with openvswitch? http://logs.openstack.org/25/64725/4/check/check-tempest-dsvm- neutron/811ce6f/logs/screen-q-dhcp.txt.gz?level=TRACE Looking at the ovs agent logs, there is a single error: http://logs.openstack.org/25/64725/4/check/check-tempest-dsvm- neutron/811ce6f/logs/screen-q-agt.txt.gz#_2014-01-07_02_00_00_640 The server instance in tempest must be getting reused because it's UUID c11cb018-0040-473d-90bb-d13a7f0d267d shows up 150 times in the neutron ovs agent logs. ** Affects: neutron Importance: Undecided Status: New ** Tags: gate-failure ** Tags added: gate-failure -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1266792 Title: test_create_list_show_delete_interfaces fails with InterfaceAttachFailed in tempest-dsvm-neutron Status in OpenStack Neutron (virtual network service): New Bug description: I couldn't find obvious existing bugs with the same failures so reporting a new one. This is a nova compute test that fails but it's failing because neutron isn't serving a port for the instance. The nova compute errors are pretty obvious but doesn't give a good reason why it fails: http://logs.openstack.org/25/64725/4/check/check-tempest-dsvm- neutron/811ce6f/logs/screen-n-cpu.txt.gz?level=TRACE The neutron server logs are full of errors, so I'm not sure which is the root cause: http://logs.openstack.org/25/64725/4/check/check-tempest-dsvm- neutron/811ce6f/logs/screen-q-svc.txt.gz?level=TRACE Looks like neutron is just dead or in terrible shape for some reason. I'm actually surprised there aren't more test failures in this run given all of the errors in the neutron logs. The errors are more limited in the dhcp agent logs, looks like a problem with openvswitch? http://logs.openstack.org/25/64725/4/check/check-tempest-dsvm- neutron/811ce6f/logs/screen-q-dhcp.txt.gz?level=TRACE Looking at the ovs agent logs, there is a single error: http://logs.openstack.org/25/64725/4/check/check-tempest-dsvm- neutron/811ce6f/logs/screen-q-agt.txt.gz#_2014-01-07_02_00_00_640 The server instance in tempest must be getting reused because it's UUID c11cb018-0040-473d-90bb-d13a7f0d267d shows up 150 times in the neutron ovs agent logs. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1266792/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
