designate quota tests may fail when being run with static Tempest credentials

[Pavlo Shchelokovskyy]

When running Tempest with static credentials (instead of creating projects/users on the fly, for example with r/o LDAP as Keystone backend) those pre-defined projects may already have configured Designate quotas that are different from the default quotas for new project in Designate.

However tests from Designate Tempest Plugin are not aware of such possibility as on many occasions they reset quotas in the project to default ones and fail when comparing with initial quotas stored at the beginning of a test.

This leads to both test failure and changed quota for a predefined project, which is bad.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/613929

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/613929
Committed: https://git.openstack.org/cgit/openstack/designate-tempest-plugin/commit/?id=8ed3b51a616fd94a39de698102ebb5dcc303dc33
Submitter: Zuul
Branch: master

commit 8ed3b51a616fd94a39de698102ebb5dcc303dc33
Author: Pavlo Shchelokovskyy <email address hidden>
Date: Thu Oct 25 19:03:46 2018 +0300

    Fix quota tests for static credentials

    when running tempest tests with static set of credentials Tempest does
    not create new tenants on the fly, and those pre-defined tenants may alreay
    have configured quotas that are different from default project ones.

    For quota tests to reliaby pass we need to store the original quotas in the
    beginning of the test and update to them in the cleanUp phase instead
    of deleting them (which resets them to the default ones).

    Change-Id: Ia1de916a97fee81148976a5b9cb134e012af8e0c
    Closes-Bug: #1800470

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/designate-tempest-plugin 0.7.0 release.