Bug 1283154 - [neutron] api error while running tempest scenario tests
Summary: [neutron] api error while running tempest scenario tests
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 5.0 (RHEL 6)
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: 5.0 (RHEL 6)
Assignee: lpeer
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-18 11:53 UTC by Daniel Mellado
Modified: 2016-04-26 15:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-15 14:04:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1381536 0 None None None Never

Description Daniel Mellado 2015-11-18 11:53:46 UTC
Description of problem:

While running neutron tempest tests in rhos, there's an occasional server fault error which makes the test fail. Restarting the neutron-server in order to enable debug seems to fix the issue, so this could be related to a race condition on the ddbb.


Version-Release number of selected component (if applicable):


How reproducible:

Run python -m testtools.run tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_subnet_details

-eventually- the test would fail and you'll get a server fault as a trace

Actual results:

TRACE neutron.api.v2.resource     "This result object does not return rows. "
TRACE neutron.api.v2.resource DBError: This result object does not return rows. It has been closed automatically.


Expected results:

The test to pass


Additional info:
Might be related to the launchpad bug attached

Comment 1 Miguel Angel Ajo 2015-12-15 10:59:56 UTC
Could you provide a more detailed trace (tempest logs + neutron server logs?)

Comment 2 Daniel Mellado 2015-12-15 14:04:10 UTC
After running it more than 20 times with the latest puddle I'm unable to reproduce the bug to post the logs, so I'll be closing it for now


Note You need to log in before you can comment on or make changes to this bug.