Adds backend propagation check for E2E recordset scenario test
It's worth adding propagation check to this test:
'test_create_and_delete_records_on_existing_zone'
This (DDT based) test covers almost all supported record types
and therefore it makes sense using a query client here
to ensure successfully create/delete of the recordset on the backends
for each tested type.
Change-Id: I4796efc3deb79b5135f667f6880349b70aa016c7
diff --git a/designate_tempest_plugin/tests/scenario/v2/test_recordsets.py b/designate_tempest_plugin/tests/scenario/v2/test_recordsets.py
index 029854a..9e5f87a 100644
--- a/designate_tempest_plugin/tests/scenario/v2/test_recordsets.py
+++ b/designate_tempest_plugin/tests/scenario/v2/test_recordsets.py
@@ -107,10 +107,12 @@
LOG.info('Ensure we respond with PENDING')
self.assertEqual('PENDING', recordset['status'])
- LOG.info('Wait until the recordset is active')
+ LOG.info('Wait until the recordset is active and propagated')
waiters.wait_for_recordset_status(self.recordset_client,
self.zone['id'], recordset['id'],
'ACTIVE')
+ waiters.wait_for_query(
+ self.query_client, recordset_data['name'], type)
LOG.info('Delete the recordset')
body = self.recordset_client.delete_recordset(
@@ -120,10 +122,13 @@
self.assertEqual('DELETE', body['action'])
self.assertEqual('PENDING', body['status'])
- LOG.info('Ensure successful deletion of Recordset')
+ LOG.info('Ensure successful deletion of Recordset from:'
+ ' Designate and Backends')
self.assertRaises(lib_exc.NotFound,
lambda: self.recordset_client.show_recordset(
self.zone['id'], recordset['id']))
+ waiters.wait_for_query(
+ self.query_client, recordset_data['name'], type, found=False)
@decorators.attr(type='slow')
@decorators.idempotent_id('cbf756b0-ba64-11ec-93d4-201e8823901f')