Ensure project is synced to Tungsten Fabric
This patch set ensures that projects are known to Tungsten Fabric
before project-specific resources (such as virtual networks) are
created.
Projects are not automatically synced from Keystone to TF.
The fqname-to-id call in resource_setup forces the synchronization.
Reference:
https: //bugs.launchpad.net/opencontrail/+bug/1685059
Change-Id: If3943572a5a05eab11c54ff4f4ad9350bce7cd23
diff --git a/tungsten_tempest_plugin/tests/api/contrail/rbac_base.py b/tungsten_tempest_plugin/tests/api/contrail/rbac_base.py
index 868631a..9c6e815 100644
--- a/tungsten_tempest_plugin/tests/api/contrail/rbac_base.py
+++ b/tungsten_tempest_plugin/tests/api/contrail/rbac_base.py
@@ -392,6 +392,9 @@
@classmethod
def resource_setup(cls):
cls.tenant_name = cls.os_primary.credentials.tenant_name
+ cls.tenant_id = cls.fq_client.fqname_to_id(fq_name=['default-domain',
+ cls.tenant_name],
+ type='project')['uuid']
@classmethod
def _try_delete_resource(cls, delete_callable, *args, **kwargs):