summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Remove PYTHONHASHSEED=0 from tox pep8 job"2Jenkins2014-10-201-1/+0
|\
| * Remove PYTHONHASHSEED=0 from tox pep8 jobJon Grimm2014-10-161-1/+0
| | | | | | | | | | | | | | | | Tempest has moved to new oslo-config-generator and this bug workaround is no longer needed. Change-Id: I50ffdcbc8a8f4830ba9c274af4c908e96467dad5 Closes-Bug: 1365136
* | Merge "Port API Tests Enhancements"Jenkins2014-10-202-1/+36
|\ \
| * | Port API Tests EnhancementsAshish Gupta2014-10-092-1/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add function to update port with security groups -Function take list of security groups name as parameter -Create security group based on the names in the parameter -Create a port without security group -Update the port with the security group -Verify that security groups are updated in the port successfully Add a test to update the port with security group -Call the update port with security groups function with one name of security group Add a test to update the port with two security group -Call the update port with security groups function with two names of security groups Change-Id: I490f3c7eb66e74f4185588870f9b2b44b54bd64b
* | | Add cleanup to test_verify_multiple_nics_orderJoseph Lanoux2014-10-171-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This test doesn't cleanup the networks and subnets that it created. Following Tempest tests in non-isolated environments are consequently failing because multiple networks are found. This change deleted those networks and subnets. Related-Bug: #1329065 Change-Id: Id618aeeb85e3d4767ed07b4d29b908274eba76df
* | | Merge "Remove OfficialClient dependency from HACKING.rst"Jenkins2014-10-171-1/+1
|\ \ \
| * | | Remove OfficialClient dependency from HACKING.rstMasayuki Igawa2014-10-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit migrates OfficialClientTest to ScenarioTest about TestVolumeBootPattern in HACKING.rst. We should not have such an example in the HACKING.rst because we don't use OfficialClientTest class in the scenario tests anymore. Partially-implements: bp:tempest-client-scenarios Change-Id: Id95d011f3d080effc7bfee6232578451f7ba72d9
* | | | Merge "Log identifiers of resources being cleaned up"Jenkins2014-10-171-0/+6
|\ \ \ \
| * | | | Log identifiers of resources being cleaned upSalvatore2014-10-161-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On teardown compute API tests clean up resources such as servers and images. This patch simply logs the identifiers of these resources in order to help debugging failures which might originate from problems during cleanup. Change-Id: Ied2924bba78ec8f4a3b51df1be69273b28362475 Related-Bug: #1357055
* | | | | Merge "Move tempest to oslo-config-generator"Jenkins2014-10-1613-1241/+713
|\ \ \ \ \ | | |_|_|/ | |/| | |
| * | | | Move tempest to oslo-config-generatorJon Grimm2014-10-1613-1241/+713
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Also fixes tempest reported bug with old generator in oslo-incubator, when identical options are registered in different groups. Change-Id: I274f48503c1b61ca09cabc8d8c50245ba1059943 Closes-bug: 1282887
* | | | | Merge "enable cinder v2 api for test_multi_backend"Jenkins2014-10-166-9/+53
|\ \ \ \ \ | |/ / / / |/| | | |
| * | | | enable cinder v2 api for test_multi_backendChandan Kumar2014-10-156-9/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | volume_type_client for v2 is added. Partially implements: blueprint cinder-v2-api-tests Change-Id: I0729eaf30946bd291f2fdaee8e99bf125e47be83
* | | | | Merge "Make rest_client.wait_for_resource_deletion timeout error more specific"Jenkins2014-10-1524-3/+124
|\ \ \ \ \
| * | | | | Make rest_client.wait_for_resource_deletion timeout error more specificMatt Riedemann2014-10-1324-3/+124
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently the timeout error message just says 'Failed to delete resource within the required time' and includes the test class/test case, but when we're seeing all volume-related tests racing with a delete hang, we can't fingerprint an elastic-recheck query on the various test class/test case names, and there aren't errors in the cinder logs. The best thing we have to fingerprint is the timeout message, but we need it to be more specific to the type of resource rather than any resource type that might have timed out during a delete operation. This is similar to the is_resource_deleted method in the various rest clients in that the concrete implementations of the base class return their specific type so we can use that in the timeout message. Closes-Bug: #1380712 Change-Id: I36b49c59daa95219c4377d1e207ea4a0c8cf8782
* | | | | | Merge "Don't use a specific arg list for stress in tox.ini"Jenkins2014-10-151-1/+1
|\ \ \ \ \ \
| * | | | | | Don't use a specific arg list for stress in tox.iniDavid Kranz2014-10-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Callers should be able to specify the arguments. Change-Id: I1d60af5e5300ff91ce3777ac46df655442098013
* | | | | | | Merge "Clean up tox.ini and make tempest and unit test distinct"Jenkins2014-10-151-42/+36
|\ \ \ \ \ \ \ | |/ / / / / /
| * | | | | | Clean up tox.ini and make tempest and unit test distinctMatthew Treinish2014-09-291-42/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit creates a separate base env for tempest tests and tempest's unit tests. However, to keep the same interface the tempest env is setup by overloading the testenv using substitution from a common base section. As part of this internal reorganization in the tox.ini several other things are cleaned up or removed. Usless or duplicate job definitions are removed. The unit tests are switched to pretty_tox. Previously they were run without any output which made it difficult to figure out exactly what was running. Additionally, this removes the unnecessary regex filter on the unit test job. The unit tests use a different discovery path so there is no need to also filter it on the same path this will allow the use of more specific regexes with tox to filter tests. Change-Id: I996d81dec2739bbe907f5fe87a335994c01697b3
* | | | | | | Merge "Easier to read console output"Jenkins2014-10-151-3/+4
|\ \ \ \ \ \ \ | |_|_|/ / / / |/| | | | | |
| * | | | | | Easier to read console outputBrant Knudson2014-09-241-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The console output was hard to read because it was displayed on one line as a string as part of a tuple. Split them up so it's readable. Change-Id: Ieb59909802a587027c4691924e70923c61476591
* | | | | | | Merge "Fix duplicate ref of volume_types_client in vol tests"Jenkins2014-10-156-65/+81
|\ \ \ \ \ \ \
| * | | | | | | Fix duplicate ref of volume_types_client in vol testsghanshyam2014-10-096-65/+81
| | |_|_|_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | tempest/api/volume/base.py admin base tests class has duplicate reference for 'volume_types_client'. Tests use mix of both. This patch fix this duplicate reference and modify tests accordingly Closes-Bug: #1379106 Change-Id: I016d364ad792c97d1dce12ee7da225ebe0a690f6
* | | | | | | Merge "Add a server console-log test with unlimited length"Jenkins2014-10-151-0/+19
|\ \ \ \ \ \ \
| * | | | | | | Add a server console-log test with unlimited lengthKen'ichi Ohmichi2014-10-101-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Now server console-log API is important for debugging gate problems and the API is called with unlimited length for debugging. However, there is not the API test with unlimited length. This patch adds the test. Change-Id: I5a35f086deddfcd54e995cb1156699592d1daea6
* | | | | | | | Merge "Add expected response checks of secgroup rules"Jenkins2014-10-151-21/+63
|\ \ \ \ \ \ \ \
| * | | | | | | | Add expected response checks of secgroup rulesKen'ichi Ohmichi2014-10-081-21/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "add security group rule" API returns additional rule in its response body but current tests don't check the response. This patch adds some checks of the response. In addition, this patch removes status code checks because the codes are already checked in client side. Change-Id: Iab4ce492c060b8a2b79a3b3d9a6d30a359f6f312 Related-Bug: #1373832
* | | | | | | | | Merge "Move status check to client for "messaging" tests"Jenkins2014-10-153-22/+24
|\ \ \ \ \ \ \ \ \
| * | | | | | | | | Move status check to client for "messaging" testsghanshyam2014-10-143-22/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch moves the response status code check from tests to client side. NOTE- Some API return different success status code on fly so leaving those status code specific check in tests only. Partially Implements blueprint: client-checks-success Change-Id: Ibbab26d6a99bf67eb684cc9c3ce7845c91fa092e
* | | | | | | | | | Merge "Fix finding router for scenario tests"Jenkins2014-10-151-2/+2
|\ \ \ \ \ \ \ \ \ \
| * | | | | | | | | | Fix finding router for scenario testsSergey Shnaidman2014-09-301-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Finding router return tuple resp,body and body only contains router details. Closes-Bug: 1375859 Change-Id: Ic405d20991561e8773153d829750826a82ed751c
* | | | | | | | | | | Merge "Fix cleanup for EC2 test_compute_with_volumes"Jenkins2014-10-151-1/+4
|\ \ \ \ \ \ \ \ \ \ \
| * | | | | | | | | | | Fix cleanup for EC2 test_compute_with_volumesghanshyam2014-10-141-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Volume cleanup for test_compute_with_volumes fails when volume is in "error" state. cleanup part destroy_volume_wait() is to delete the volume and detach before delete if necessary. In destroy_volume_wait(), before detaching the volume there is checks if volume status is not "available" but that is not sufficient enough to guarantee that volume is attached. Volume status can be "error". When something wrong happens with Volume and Volume is in "error" state then, detach request will through the error as mentioned in bug# 1310896. Logic in destroy_volume_wait should be checking of state as "in-use" before trying to detach volume. So that if it is in "in-use" state then detach and go for volume delete. If not in "in-use" ("available" or "error" etc) then only go for volume delete. Change-Id: I1882dbba947cc294cb4fe119db50f2a1c23b75be Related-Bug: #1310896
* | | | | | | | | | | | Merge "Add missing space to build_timeout description"Jenkins2014-10-152-2/+2
|\ \ \ \ \ \ \ \ \ \ \ \
| * | | | | | | | | | | | Add missing space to build_timeout descriptionEric Harney2014-10-142-2/+2
| |/ / / / / / / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Change-Id: I2b4ceb5c4c795903454873a6d4882c563499186a
* | | | | | | | | | | | Merge "Adds status check for FloatingIP in network scenarios"Jenkins2014-10-154-5/+49
|\ \ \ \ \ \ \ \ \ \ \ \
| * | | | | | | | | | | | Adds status check for FloatingIP in network scenariosYair Fried2014-10-054-5/+49
| | |_|_|_|_|_|_|_|_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Verifies FloatingIP changes status correctly on association and dis-association Scenarios: test_network_basic_op test_network_advanced_server_ops Status is verified after connectivity check and without a waiter in order to not mask unknown races in Neutron Changes show() to refresh() to keep consistency Partially Implements: blueprint fip-op-status (this is a Neutron bp: https://blueprints.launchpad.net/neutron/+spec/fip-op-status) Partially Implements: blueprint neutron-advanced-scenarios Change-Id: Ibd45f3092cebc8f9fd0d16a3a543c2ef72156409
* | | | | | | | | | | | Merge "Orchestration use stack timeout waiting for ping response"Jenkins2014-10-152-5/+6
|\ \ \ \ \ \ \ \ \ \ \ \
| * | | | | | | | | | | | Orchestration use stack timeout waiting for ping responseSteven Hardy2014-10-082-5/+6
| | |_|_|_|_|_|_|_|_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The test_server_cfn_init scenario test boots a full Fedora image, not the cirros image which is presumably used for compute tests where the default 120s ping timeout may be appropriate. To ensure we don't encounter any spurious failures due to booting the much bigger orchestration image (which is Fedora in the gate), use the stack timeout (default 900s) to override the ping timeout for this test. Change-Id: I4eba18333bdaa0ef41122cda85fd3f4d91b2cf5c Closes-Bug: #1374175
* | | | | | | | | | | | Merge "Add Credentials Provider factory"Jenkins2014-10-1420-188/+196
|\ \ \ \ \ \ \ \ \ \ \ \
| * | | | | | | | | | | | Add Credentials Provider factoryAndrea Frittoli2014-10-0920-188/+196
| | |/ / / / / / / / / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a method to select the appropriate credentials provider based on configuration, and replace all the flow branches based on allow_tenant_isolation to use the factory. This also includes handling NotImplemented exceptions on admin creds for scenarios tests which is a new potential condition by using the factory. Partially-implements bp:test-accounts Change-Id: I280f2b1659c593e14ab9213a161b55bcfc08fa5c
* | | | | | | | | | | | Merge "Verify network interfaces are in requested order"Jenkins2014-10-142-2/+40
|\ \ \ \ \ \ \ \ \ \ \ \
| * | | | | | | | | | | | Verify network interfaces are in requested orderJoseph Lanoux2014-10-142-2/+40
| | |_|_|_|_|_|_|/ / / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There is no Tempest test verifying that the order of multiple networks passed to an instance during its creation is preserved within the instance (https://review.openstack.org/#/c/85711/). This change introduces a new test in test_create_server to verify this feature. Change-Id: I3622b9e8dfbbf73eb9a0a69d2094b75e4934fe17
* | | | | | | | | | | | Merge "Remove @author tags from copyright statements"Jenkins2014-10-142-5/+0
|\ \ \ \ \ \ \ \ \ \ \ \
| * | | | | | | | | | | | Remove @author tags from copyright statementsChristian Berendt2014-10-092-5/+0
| |/ / / / / / / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We have git to track the authorship of files. It is not necessary to use the @author tags in the copyright statements. Change-Id: I67163ffe46540423ca1f5584881d7c2db47fe276
* | | | | | | | | | | | Merge "Run telemetry in javelin if resources.yaml says so"Jenkins2014-10-142-0/+3
|\ \ \ \ \ \ \ \ \ \ \ \
| * | | | | | | | | | | | Run telemetry in javelin if resources.yaml says soChris Dent2014-10-112-0/+3
| |/ / / / / / / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In previous code telemetry checks were always run (if there were servers to check). If the environment did not have ceilometer services this would fail. check_telemetry now checks that there is a true value on the 'telemetry' key in resources.yaml. No configuration is required for the telemetry checks, so only a key with a value is required. Change-Id: I84e0f5938ec808537043dba29a896f991779b04c
* | | | | | | | | | | | Adds TestSecurityGroupsBasicOps created VM's security_groups checkClaudiu Belu2014-10-141-1/+5
| |_|_|/ / / / / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In nova.compute.manager.ComputeManager._build_instance, there is the following code: if request_spec and self.is_neutron_security_groups: security_groups = request_spec.get('security_group') else: security_groups = [] Which will verify this from nova.network.security_group.openstack_driver: def is_neutron_security_groups(): return CONF.security_group_api.lower() in ('neutron', 'quantum') This basically means that if the Nova compute node's nova.conf does not contain security_group_api=neutron, the created VMs security_groups will be [], which later will be default. This commit checks the created VM's security_groups, this way it makes sure that the created security group rules will be applied to the VM. Closes-Bug: #1364015 Change-Id: I444c128b6be01e29dd95c8727b7fb676e3dc4eed
* | | | | | | | | | | Merge "Add exceptions.BadRequest to the test case of reserve_fixed_ip"Jenkins2014-10-141-1/+4
|\ \ \ \ \ \ \ \ \ \ \ | |_|_|_|_|/ / / / / / |/| | | | | | | | | |
| * | | | | | | | | | Add exceptions.BadRequest to the test case of reserve_fixed_ipEli Qiao2014-10-131-1/+4
| | |_|_|_|_|_|_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | we change the exception of reserve_fixed_ip in fixed_ip api to HTTPBadRequest, add this exception to tempest, and also we need to accept HTTPNotFound exception to support juno test cases. Change-Id: Iafd2fb82ad5d50c2f4b3f0819ac7a6f8aa901264