I am not sure that using project_id would help as (at least as I know) we have 2 projects: admin & tenant, so possibly other resources (trunks in this case) will have the same project_id. What about changing names to be more specific for the given testclass: https://opendev.org/openstack/neutron-tempest-plugin/src/branch/master/neutron_tempest_plugin/api/test_trunk.py#L317 If I understand the names are in a list here: https://opendev.org/openstack/neutron-tempest-plugin/src/branch/master/neutron_tempest_plugin/api/base.py#L1203
so when in test_trunk.py the names are used in the loop to create trunks, just add __name__ to the fetched name chunks: for name in cls.resource_names: .... cls.create_trunk(parent_port, name='%s%s' % (name, cls.__name__))
I am not sure that using project_id would help as (at least as I know) we have 2 projects: admin & tenant, so possibly other resources (trunks in this case) will have the same project_id. /opendev. org/openstack/ neutron- tempest- plugin/ src/branch/ master/ neutron_ tempest_ plugin/ api/test_ trunk.py# L317 /opendev. org/openstack/ neutron- tempest- plugin/ src/branch/ master/ neutron_ tempest_ plugin/ api/base. py#L1203
What about changing names to be more specific for the given testclass:
https:/
If I understand the names are in a list here:
https:/
so when in test_trunk.py the names are used in the loop to create trunks, just add __name__ to the fetched name chunks: create_ trunk(parent_ port, name='%s%s' % (name, cls.__name__))
for name in cls.resource_names:
....
cls.