Description of problem:
The tempest test neutron_tempest_plugin.api.admin.test_quotas.QuotasTest.test_detail_quotas is failing for OVN with:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/tempest/common/utils/__init__.py", line 107, in wrapper
return func(*func_args, **func_kwargs)
File "/usr/lib/python2.7/site-packages/neutron_tempest_plugin/api/admin/test_quotas.py", line 145, in test_detail_quotas
File "/usr/lib/python2.7/site-packages/testtools/testcase.py", line 350, in assertEqual
self.assertThat(observed, matcher, message)
File "/usr/lib/python2.7/site-packages/testtools/testcase.py", line 435, in assertThat
testtools.matchers._impl.MismatchError: 1 != 2
The reason of the failure has to deal with the networking-ovn's metadata implementation. Basically, when metadata is enabled (and it's for the CI) and we create a network resource for OVN, networking-ovn will also allocate a port to be used by the metadata agent .
That port will deduct 1 from the user's quota for ports and that is causing the difference there which is making the test fail.
Since this is an API test (that runs when the quota_details API extension for neutron is enabled) I think that there's little to us to do to fix it without having to do a big refactor in the networking-ovn's code, which I don't think is worth of it to fix this test.
Perhaps, disabling that extension in the CI for now would be the easiest way to deal with the problem.
Version-Release number of selected component (if applicable):
The patch  uses a different approach and calculates the number of used ports on that test after the network has been created. Perhaps that's more generic and doesn't require disabling the test or the extension for OVN.
*** Bug 1575844 has been marked as a duplicate of this bug. ***
Patch is merged upstream
Fix verified on osp13z2
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible.
If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-".
To add draft documentation text:
* Select the documentation type from the "Doc Type" drop down field.
* A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.
(In reply to Joanne O'Flynn from comment #17)
> This bug is marked for inclusion in the errata but does not currently
> contain draft documentation text. To ensure the timely release of this
> advisory please provide draft documentation text for this bug as soon as
> If you do not think this bug requires errata documentation, set the
> requires_doc_text flag to "-".
> To add draft documentation text:
> * Select the documentation type from the "Doc Type" drop down field.
> * A template will be provided in the "Doc Text" field based on the "Doc
> Type" value selected. Enter draft text in the "Doc Text" field.
This bug is only related to a test run so I don't think it needs any documentation about it. I've set the requires_doc_text flag to "-" as requested for this case.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.