commit bac51dc2d6699217a4f0aab705c241776cc503a6
author Itzik Brown <itzikb@redhat.com> Mon Oct 31 12:25:04 2016 +0000
committer Itzik Brown <itzikb@redhat.com> Mon Nov 21 19:51:56 2016 +0200
tree 11ac0ef1a5d89294cfa97274017ee14e0be4d78d
parent 1bf6a1dca7fc2ea94e29806c2ae040351fd20a3a

Using a new security group in scenario tests

Instead of using the default security group - creating and
using a new security group in setup_network_and_server.
This should help when two tests are in the same class and have the
same tenant which can cause problems when one test is changing the
security group, adding rules etc.

Also adding resource cleanup in API tests base for security groups.

Change-Id: I4997bb48edf05402aa8135e3fd70e4c16cafb114

neutron/tests/tempest/scenario/test_qos.py

diff --git a/neutron/tests/tempest/scenario/test_qos.py b/neutron/tests/tempest/scenario/test_qos.py
index 89b31a7..a58b6e4 100644
--- a/neutron/tests/tempest/scenario/test_qos.py
+++ b/neutron/tests/tempest/scenario/test_qos.py
@@ -158,7 +158,9 @@
                      'port_range_min': NC_PORT,
                      'port_range_max': NC_PORT,
                      'remote_ip_prefix': '0.0.0.0/0'}]
-        self.create_secgroup_rules(rulesets)
+        self.create_secgroup_rules(rulesets,
+                                   self.security_groups[-1]['id'])
+
         ssh_client = ssh.Client(self.fip['floating_ip_address'],
                                 CONF.validation.image_ssh_user,
                                 pkey=self.keypair['private_key'])