This new test is checking that, by default, the quota engine will check
the resource usage before setting the quota. If the new quota is below
the resource usage, an exception is returned.
This patch is also adding the flag "force=True" in other tests setting
quotas for resources; these tests do not need the quota engine to
verify the current resource usage.
Related-Bug: #1953170
Change-Id: Ia193cd5a2aacc4243b5807eb7757b32e66f12365
This patch adds test which replaces fullstack test:
neutron.tests.fullstack.test_securitygroup.SecurityGroupRulesTest.test_normalized_cidr_in_rule
It is simple API test which can be done quickly in
neutron-tempest-plugin job. In fullstack instead it requires to prepare
whole environment with neutron-server, fake compute
node, agents, etc. so it takes much more time.
Change-Id: I4124f7f0a2edfe28c95693280b6490c8884fce11
This patch adds new test which checks if SG rules actually created
automatically for new default and non-default SG are matching template
rules from neutron DB.
Depends-On: https://review.opendev.org/c/openstack/neutron/+/884474
Related-bug: #1983053
Change-Id: Ica0810413bef7f0e3e6dff21f6c9e4cda1945a43
The tenant_id property of RestClient in tempest was deprecated in
25.0.0. This replaces the deprecated property by the new project_id
property to avoid the following warning.
WARNING tempest.lib.common.rest_client [-] Deprecated: "tenant_id"
property is deprecated for removal, use "project_id" instead
Depends-on: https://review.opendev.org/c/openstack/tempest/+/707938
Change-Id: Ie3c32f9f2278b78603a4214c5717df8691ba490a
With this patch most of the API tests related to Security groups will be
run for the default (stateful) security groups and also for stateless
security groups by passing "stateful=False" to the
create_security_group() function.
Change-Id: I66af24513ba126c1cd00ca896bbd56a448faf726
It's a simple test case that creates, updates a stateless SG and
checks that the attribute is updated accordingly.
Related-Bug: #1949451
Depends-On: I85f7749e7e6186b9e3a7534bce6c306b18702333
Change-Id: I30e0a11c45618cbdaa0130942cb67ea99bbd0b92
Security group rules created by SecGroupRulesQuotaTest are not
being cleaned up after TC execution. Security Group rules normally
would get cleanup if associated Security Group is deleted. However,
SecGroupRulesQuotaTest doesn't create any Security Groups. The
Security Group rules are created in default or existing Security
Groups. Thus, the SecGroupRulesQuotaTest should be responsible to
clean up the rules which created by the TC.
Change-Id: I4dd2d9eb7e60101ba7f5c3d915ec27ee6c46b227
Test scenario:
Create a number of security groups using the same name.
Make sure that all the security groups have been created successfully
and that each group has its own unique ID.
Change-Id: I044e8f86cd8999d1bde5e4995239b0dfa55489f0
The test is checking that its possible to decrease
Security group rules quota less than already created.
Change-Id: I6a170a153038380d2fe5632afcab47b1cdba5f6c
The test actually tries to create security group rules
while the quota is disable. The goal is to check that we
are not enforce SG rules quota while it disabled.
Change-Id: I504b98ecaa3346799b0a09ec93894472794d4635
The test is checking that it is possible to create
new security group rules after increasing the quota parameter.
Change-Id: Ie961293215c48883c962debe888b0bca418e3eb9
The helper class contain:
-Get function of security group rules quota
-Set function of security group rules quota
-Increase & Decrease of security group rules quota
Change-Id: I99d633bdc0fbac7d7259210052be289c94b70a2b
1. Test supported values for securiyt group quota
2. Test creating maximum allowed amount of security groups
3. Test creating maximum allowed amount of security groups if
quota is increased
4. Test decreasing security group quota to a value that is less
than amount of already created security groups
5. Test creating security groups when the quota is disabled (set to -1)
Change-Id: I833e5d5e67ef7555c9e6a54613b7324310079b0b
A neutron change, https://review.opendev.org/#/c/453346/
is standardizing the protocol name for IPv6 ICMP in security
group rules to be 'ipv6-icmp', even if 'icmp' or 'icmpv6'
was passed during creation. Change the API test to check
against a list of possible values so it covers both old and
new behaviors.
Change-Id: I0ca8d743ca56f7d67ef8c1ae45ca518bd6e6dc35
Partial-Bug: #1582500
Change I50858d5198d8a70a2bb9fb278786c433d7cb12ca improved
test case methods for helping reducint test case complexity
when handling with security groups.
This change use those API improvements to reduce the
complexity of existing test cases and to make them easier
to read.
Change-Id: I8589b31db996702c3da2235fa72182badfd84c02
* The following commit sync the code from following hash:
start_hash: 7279aa35851110a4933a10b58b2758a2bc3933a3
end_hash: 6e911a49a9e630878f4c46f61fde3964be550880
Change-Id: I371aa4d5f043f695df04b98b0f485c8f0548f2b3
* switch from neutron.tests.tempest to neutron_tempest_plugin
* Cleaned up README.rst and setup.cfg
* Use neutron_tempest_plugin as a tempest plugin package
* Fixed gitreview
* Keeping flake8 Ignores in tox.ini as tempest plugin is
imported from neutron codebase.
Change-Id: I42d389836e72813fdeebc797a577f4a8ac2ee603
