designate tempest plugin tests fail with default quota_zones setting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
Undecided
|
Pavlo Shchelokovskyy |
Bug Description
When designate is configured with default setting for zone quotas (10) various tests from designate-
I see that designate devstack plugin hard-sets the default quotas for zones in designate to 100 instead of 10 (default for this config option in service) and thus tests do not fail on upstream gates, however this makes running them against a production deployed OpenStack cloud too fragile.
We should make the tests smarter in this regard.
Example failure:
designate_
-------
Captured traceback:
~~~~~~~~~~~~~~~~~~~
Traceback (most recent call last):
File "/usr/local/
return func(self, *args, **kwargs)
File "/usr/local/
post_model = data_utils.
File "/usr/local/
resp, body = self.zones_
File "/usr/local/
return f(*args, **kwargs)
File "/usr/local/
resp, body = self._create_
File "/usr/local/
extra_headers=
File "/usr/local/
return self.request(
File "/usr/local/
self._error_
File "/usr/local/
raise exceptions.
tempest.
Details:
{u'code': 413, u'type': u'over_quota', u'request_id': u'req-558a928d-
description: | updated |
It seems that at least the test_in recordset_ validation. py is to blame. It creates zone for each test but does not clean them up after the test. As a result, tests in this class leave behind zones that saturate the small default quota).