Bug 1230840
Summary: | Tempest needs additional configuration to run successfully | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | David Kranz <dkranz> | ||||
Component: | rhosp-director | Assignee: | Imre Farkas <ifarkas> | ||||
Status: | CLOSED ERRATA | QA Contact: | yfried | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 7.0 (Kilo) | CC: | astafeye, athomas, calfonso, dkranz, dnavale, mburns, ohochman, rhel-osp-director-maint, rrosa, yeylon | ||||
Target Milestone: | ga | Keywords: | Triaged | ||||
Target Release: | Director | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | python-rdomanager-oscplugin-0.0.8-31.el7ost | Doc Type: | Bug Fix | ||||
Doc Text: |
Previously, deployment specific values were not provided in OpenStack Integration Test Suite (tempest), resulting in the failure of some tempest tests.
With this update, a '--deployer-input' flag is added for the 'openstack overcloud validate' command so the administrator can provide a file (tempest.conf) containing the deployment specific values. As a result of using the '--deployer-input filename' flag, fewer tests result in failure.
|
Story Points: | --- | ||||
Clone Of: | |||||||
: | 1249640 (view as bug list) | Environment: | |||||
Last Closed: | 2015-08-05 13:53:19 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1249640 | ||||||
Attachments: |
|
Description
David Kranz
2015-06-11 15:28:17 UTC
[object-storage] # Role to add to users created for swift tests to enable creating # containers (string value) #operator_role = Member # User role that has reseller admin (string value) #reseller_admin_role = ResellerAdmin # Name of sync realm. A sync realm is a set of clusters that have # agreed to allow container syncing with each other. Set the same # realm name as Swift's container-sync-realms.conf (string value) #realm_name = realm1 # One name of cluster which is set in the realm whose name is set in # 'realm_name' item in this file. Set the same cluster name as Swift's # container-sync-realms.conf (string value) #cluster_name = name1 re-targeting to GA : We're suspecting this bug related to many of the FAILED (failures=245) that we're getting when running tempest as - post-deployment-validation against the overcluod - using the command "openstack overcloud validate " Results: Traceback (most recent call last): File "/home/stack/tempest/tempest/api/network/admin/test_external_network_extension.py", line 106, in test_delete_external_networks_with_floating_ip enable_dhcp=False) File "/home/stack/tempest/tempest/api/network/base.py", line 240, in create_subnet raise exceptions.BuildErrorException(message) BuildErrorException: Server %(server_id)s failed to build and is in ERROR status Details: Available CIDR for subnet creation could not be found Ran 807 tests in 7092.710s FAILED (failures=245) Sorry, looks like I forgot these. They may not all be necessary. [network] # The cidr block to allocate tenant ipv4 subnets from (string value) #tenant_network_cidr = 10.100.0.0/16 # The mask bits for tenant ipv4 subnets (integer value) #tenant_network_mask_bits = 28 # The cidr block to allocate tenant ipv6 subnets from (string value) #tenant_network_v6_cidr = 2003::/48 # The mask bits for tenant ipv6 subnets (integer value) #tenant_network_v6_mask_bits = 64 # Default floating network name. Used to allocate floating IPs when # neutron is enabled. (string value) #floating_network_name = <None> # List of dns servers which should be used for subnet creation (list # value) #dns_servers = 8.8.8.8,8.8.4.4 # vnic_type to use when Launching instances with pre-configured ports. # Supported ports are: ['normal','direct','macvtap'] (string value) # Allowed values: <None>, normal, direct, macvtap #port_vnic_type = <None> I tried to figure out the values for each of the config options. None of these are included amongst the parameter we are passing to heat (I added the output of a heat stack-show command, so you can check it). I also tried to check different config files on the deployed overcloud with the same result. Eg. even is 'change_password' is listed in the compute-feature-enabled group, it's not included nova.conf. Could you please comment on each of those options on how/where to check the values on a deployment? Created attachment 1042257 [details]
output of heat stack-show overcloud
There is not necessarily a name-match between a feature-enabled item in tempest.conf and some option in nova.conf, cinder.conf, etc. For many of these values the defaults will be ok. If the comments in tempest.conf.sample are not sufficient to determine whether a cloud has the feature, the definitive explanation is which tests are skipped based on its absence. In some cases some one who has details of how the service in question is deployed by Director will need to be consulted. WIP patch already proposed: https://review.gerrithub.io/#/c/238706/ It generates a partial tempest config and passes it to config_tempest.py which processes it properly. I still have problems with figuring out what the values should be as mentioned in Comment 6. I sent an email about the network part to the mailing list: http://post-office.corp.redhat.com/archives/openstack-management-team-list/2015-July/msg00292.html Considering the implications of #1241583, it might not even make sense to generate the partial tempest configuration as it will depend on how the deployer configures the network. As an alternative, we can provide a flag to overcloud validate so a partial tempest config written by the administrator could be passed. Patch merged in rdo-management/python-rdomanager-oscplugin: https://github.com/rdo-management/python-rdomanager-oscplugin/commit/b728836ae7fe0766800582728f1afd9b00b92158 Downstream patch proposed: https://code.engineering.redhat.com/gerrit/#/c/52764/ What is the validation steps ? (David) The validation is using the additional flag with the reproduction steps? (Imre) Hi, I have limited tools for the bug verification so it would be great if you could check the fix. tnx According to David, this bug isn't solved. Please consider the scope change for 7.0 as described in Comment 13 and Comment 14 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2015:1549 |