This reverts commit 07c92e1bf3013b949804e5b0020677843a640441.
This currently locks up the neutron gate because of ip exhaustion.
Change-Id: Ia441e854e0d3e1da1c55a685045d935da3dc3c64
DeletableSubnet._router_ids was defined as a static attribute, causing
errors on tearDown working with multiple {router,subnet} couples as it
tries to disconnect subnet from all routers existing instead of all
routers connected to it
Change-Id: Id446d7bb2be117ea56b52e6a644b259089cdc158
add following negative test cases:
1. delete non existent secgroup
2. create rule with invalid protocol name
3. create rule with invalid port
Change-Id: Iad17f9b163ba33297edd1e0b8ba14194050c878b
This commit just adds the use of isolated credentials to the neutron
api tests if tenant isolation is enabled. Previously the neutron
tests would all run in the same tenant regardless of the config
option.
Change-Id: Ide9c4a3ed543b917bd401561c601f9897bd7db50
The value "" will be consider as None, when API receive it.
But "None" will be consider as the string "None"
Closes-Bug: 1241397
Change-Id: I01f25dcc073684b1843abeb5814bc22b0520c5b1
In many tempest tests, we use rand_name(). However, these generated
names are very general. So it is difficult to distinguish the resource
is generated from Tempest or not.
And, in many tests, we use rand_name() with '-' suffix such as
rand_name('foo-'). I think this is not smart.
So this commit injects "-tempest-" to rand_name().
And, by this commit, the generated rand name will include "--" such as
'foo--tempest-123'.
So I will fix them in another commit.
Change-Id: I7bb8f5bbe2346b0b0ab6e91757e20a67b9098f8a
Several test cases like quota related tests should not be done without
creating a new tenant in all cases.
This change enforces the isolated code path for the nova quota tests.
These tests requires admin rights anyway, so probably no one want to
try to run them without admin permissions.
Change-Id: Ib7550bc68f493ce9c6acbd57fc2d901e14ec2fef
this does refactor in compute.base, add BaseV2ComputeTest as
the base class of nova v2 api test. Because there will be nova
v3 tests, this change will be convenient to add BaseV3ComputeTest
as the base class of nova v3 api tests. In this way, we can split
v2 tests with v3 tests easily, and share some common method.
Partially implements blueprint nova-v3-api-tests
Change-Id: Ie8e0d17a95e8378733dd21ab341dfad1331edf6e
Here changed the exception name for
http error code 409 from Duplicate to Conflict
and error code 500 from ComputeFault to ServerFault.
Change-Id: Ifbebd8761ac8402308e9d37ec78468c65539ac1a
Two test case in the test_servers_negative change the 'one' servers
into a stable not active state. We are waiting 2 times 400 sec for
getting active state in vain.
Having those test cases to restore the expected state.
The deleted server related rebuild and reboot test case create are
merged and it creates and deletes one server.
Change-Id: Ie1b9dc62bad2bf7b8595da2c9d6f994c646a0025
This commit just adds a skip decorator for 2 neutron tests that don't
work in the gate either because of improper test setup or missing
devstack configuration.
Related-Bug: #1240694
Change-Id: I508aaf3dbc49c326cd54e2008f3e14935f23056e
Adding testcases for vpn service create, list, delete, and show
part of blueprint: vpnaas-api-test-cases
Change-Id: I015fd503a198f93bfc7382e30b2aff5c74b3fd30
Change I5187a109f0bacb1f3afa4276b3d73f47fd53ad87 re-enabled some
negative quota tests for compute but they don't work if you're using
Neutron due to nova bug 1186354.
There is a patch up for the bug here:
https://review.openstack.org/#/c/43822/
but it's taking awhile to land so we should skip the tests until that's
working.
Partial-Bug: #1186354
Change-Id: I0458f8cf95585962638a82da34397071e34a1940
Now operations started with the server when it's task state was not
None. Ie. Idle / 'ready for action'.
The wait for wait_for_server_status method implicitly waits for the None
task state, it should be able to fix the issue.
The server will be rebuilded if otherwise it cannot be move to a clean active
state, this issue will be logged.
It is an unexpected exception, so the log verifier should be able to
report it.
Fixing bug 1218391
Change-Id: Ib0e90a06e0e34f134bcca74712939e87e235c1ea
this add test for updating server's disk_config tests. And use
addCleanup to manager server resource instead of deleting server
at end of these tests in this file.
Change-Id: I2ed90456e86f6e8c6e7d0b954bf381d944a6ca53
