RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1226969 - Tempest failed when running after overcloud deployment
Summary: Tempest failed when running after overcloud deployment
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: rdo-manager
Version: Kilo
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: RC
: Kilo
Assignee: Hugh Brock
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-01 14:49 UTC by mathieu bultel
Modified: 2016-05-19 15:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 15:57:40 UTC
Embargoed:


Attachments (Terms of Use)
tempest-run.log (23.77 KB, text/plain)
2015-06-01 14:49 UTC, mathieu bultel
no flags Details

Description mathieu bultel 2015-06-01 14:49:28 UTC
Created attachment 1033376 [details]
tempest-run.log

When follow the basic deployment of overcloud (https://repos.fedorapeople.org/repos/openstack-m/docs/master/basic_deployment/basic_deployment.html)
and run the command :

instack-deploy-overcloud --tuskar --tempest

Tempest fail during the execution :
(environment :
Instack on virtual machine : 1 undercloud, 2 overcloud)

The latest tests print on the console screen, before lost the connection of the instack virtual machine.
(see tempest.log in attachment and tempest-run.log)

>>>
tempest.api.compute.servers.test_servers.ServersTestJSON
    test_create_server_with_admin_password[id-b92d5ec7-b1dd-44a2-87e4-45e888c46ef0]OK  3.06
    test_create_server_with_ipv6_addr_only[id-38fb1d02-c3c5-41de-91d3-9bc2025a75eb]FAIL
    test_create_specify_keypair[id-f9e15296-d7f9-4e62-b53f-a04e89160833]FAIL
    test_create_with_existing_server_name[id-8fea6be7-065e-47cf-89b8-496e6f96c699]FAIL
    test_update_access_server_address[id-89b90870-bc13-4b73-96af-f9d4f2b70077]FAIL
    test_update_server_name[id-5e6ccff8-349d-4852-a8b3-055df7988dd2]  FAIL
    test_update_server_name_in_stop_state[id-6ac19cb1-27a3-40ec-b350-810bdc04c08e]FAIL
setUpClass (tempest.api.compute.servers.test_servers_negative
    ServersNegativeTestJSON)                                          FAIL
setUpClass (tempest.api.compute.servers.test_virtual_interfaces
    VirtualInterfacesTestJSON)                                        FAIL
tempest.api.compute.servers.test_virtual_interfaces_negative.VirtualInterfacesNegativeTestJSON
    test_list_virtual_interfaces_invalid_server_id[id-64ebd03c-1089-4306-93fa-60f5eb5c803c,negative,network]FAIL
setUpClass (tempest.api.compute.test_authorization
    AuthorizationTestJSON)                                            FAIL
tempest.api.compute.test_extensions.ExtensionsTestJSON
    test_get_extension[id-05762f39-bdfa-4cdb-9b46-b78f8e78e2fd]       OK  0.33
    test_list_extensions[id-3bb27738-b759-4e0d-a5fa-37d7a6df07d1]     OK  0.09
tempest.api.compute.test_live_block_migration_negative.LiveBlockMigrationNegativeTestJSON
    test_invalid_host_for_migration[id-7fb7856e-ae92-44c9-861a-af62d7830bcb,negative]FAIL
setUpClass (tempest.api.compute.test_networks
    NetworksTestJSON)                                                 SKIP  0.00
tempest.api.compute.test_quotas.QuotasTestJSON
    test_compare_tenant_quotas_with_default_quotas[id-cd65d997-f7e4-4966-a7e9-d5001b674fdc]OK  0.51
    test_get_default_quotas[id-9bfecac7-b966-4f47-913f-1a9e2c12134a]  OK  0.02
    test_get_quotas[id-f1ef0a97-dbbb-4cca-adc5-c9fbc4f76107]          OK  0.06
tempest.api.compute.test_tenant_networks.NetworksTestJSON
    test_list_show_tenant_networks[id-edfea98e-bbe3-4c7a-9739-87b986baff26]OK  0.90








Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Chandan Kumar 2016-05-19 15:57:40 UTC
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.


Note You need to log in before you can comment on or make changes to this bug.