Tempest tests cannot run in parallel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-sfc |
New
|
Undecided
|
maestropandy |
Bug Description
Currently, tempest tests need to be run sequentially, or else they fail with bugs like bug #1655618
Tests work for now with this workaround:
https:/
But they should be updated to allow parallel runs (http://
One of the identified reasons is flow classifier parameters are identical between tests, so this generates conflicts like:
Details: {u'type': u'PortChainFlow
But there may be more problems to fix before having parallel-capable tempest tests
description: | updated |
Changed in networking-sfc: | |
assignee: | nobody → maestropandy (maestropandy) |
To expend on the PortChainFlowCl assifierInConfl ict issue:
tests create a flow classifier with parameters logical source port, source ip prefix, destination ip prefix
The logical source port is ignored for the conflict check, so if the server IP addresses are identical it will conflict. The flow classifiers should be different for each test (force separate IP addresses, add extra parameters, ...)