"test_show_port_chain" conflicts with Flow Classifier

[Rodolfo Alonso]

Test case: neutron_tempest_plugin.sfc.tests.api.test_sfc_extensions.SfcExtensionTestJSON.test_show_port_chain

Error:
```
Details: {'type': 'PortChainFlowClassifierInConflict', 'message': 'Flow Classifier a3d6ec45-5ea8-4e3a-a602-d24baa3ca360 conflicts with Flow Classifier a978b8ee-651b-4a7f-9475-58b224486827 in port chain b9fb54ee-1868-46ba-9abd-b09e69360a2d.', 'detail': ''}
```

Log: https://storage.bhs1.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_6e4/692822/4/check/neutron-tempest-plugin-sfc/6e436c3/testr_results.html.gz

[Ryan Tidwell (ryan-tidwell)]

A quick glance through open reviews against neutron-tempest-plugin indicates this is an intermittent issue, am I mistaken?

[Slawek Kaplonski (slaweq)]

You're right Ryan. This happens from time to time so I think that this is kind of race condition in the tests probably.

[Bernard Cafarelli (bcafarel)]

Just remembering that "old" in-repo tempest tests were running with OS_TESTR_CONCURRENCY=1 there is probably a LP for networking-sfc about parallel tests still open

Though I had made some changes (unique IDs etc) at some point that should allow parallel run, it looks like there is still something to fix

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.opendev.org/695201

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/695201
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=f2beb170b21c5ac09f90d3bbae6735a0db43ba7e
Submitter: Zuul
Branch: master

commit f2beb170b21c5ac09f90d3bbae6735a0db43ba7e
Author: Bernard Cafarelli <email address hidden>
Date: Wed Nov 20 15:01:13 2019 +0100

    Temporarily limit SFC testing concurrency

    Tests mostly run in parallel now, but this is not perfect yet. Set
    concurrency to 1 until relatd bug is properly fixed

    Change-Id: Ic3ed0c56c71a16cc6dcd2fc6f3c144c18e5be0ed
    Related-Bug: #1851500
    Related-Bug: #1660366

[yatin (yatinkarel)]

I think this can be closed as issue not seen after reducing concurrency. Increasing concurrency can be a seperate task altogether.